|
Thanks for your quick reply Rob. I would do left outer joins but 1) The files are too big and when we do left outer joins it takes too long. 2) I have to do one or more passes based on if the first pass worked or not. I would user SQL RPG but I'm trying to get this up and running fast. Wes <rob@xxxxxxxxx> wrote in message news:OF2AB18102.7C905B5B-ON05256F9A.005E4C62-05256F9A.005E509A@xxxxxxxxxxxx > Left outer join? > > Rob Berendt > -- > Group Dekko Services, LLC > Dept 01.073 > PO Box 2000 > Dock 108 > 6928N 400E > Kendallville, IN 46755 > http://www.dekko.com > > > > > > "Wes" <small_du@xxxxxxxxx> > Sent by: midrange-l-bounces+rob@?> EÞ?ÙyéLÙwn > 01/31/2005 11:58 AM > Please respond to > Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> > > > To > midrange-l@xxxxxxxxxxxx > cc > > Subject > SQL Proc and Data Not Found > > > > > > > I'm writing a proc where I have a cursor and for each row found in the > cursor I do a select from other files. I'm monitoring for record not found > conditions for the cursor. My question is how do I trap rows not found for > the select statements other than the cursor? I don't want my program to > exits just because it can't find a record in the select statement. > > > > DECLARE CONTINUE HANDLER FOR not_found > SET at_end = 1; . > . > . > . > OPEN C1; > > FETCH C1 INTO v_mcu, v_Emcu, v_Company_ID, v_Ord_#, v_Ord_Type, > v_TankID, v_an8, v_shan, v_Ord_Date, v_GL_Date, > v_Act_Ship_Date, v_Short_Item#, v_Item, > v_UOM, v_Ship_qty, v_Vol, v_unit_price , > v_Ext_Amount, v_unit_cost, v_Ext_Cost, v_GLC; > WHILE at_end = 0 DO > -- SET DATE > > SELECT UDVMCU, UDTRP INTO v_Trip_Depo, v_Delivery_# > FROM F49211 > WHERE UDDOCO = v_Ord_# > and UDDCTO = v_Ord_Type > and UDLNID = v_Line_ID > and UDKCOO = v_Company_ID; > > > > > Thanks, Wes > > > > -- > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing > list > To post a message email: MIDRANGE-L@xxxxxxxxxxxx > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/mailman/listinfo/midrange-l > or email: MIDRANGE-L-request@xxxxxxxxxxxx > Before posting, please take a moment to review the archives > at http://archive.midrange.com/midrange-l. > > > -- > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list > To post a message email: MIDRANGE-L@xxxxxxxxxxxx > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/mailman/listinfo/midrange-l > or email: MIDRANGE-L-request@xxxxxxxxxxxx > Before posting, please take a moment to review the archives > at http://archive.midrange.com/midrange-l. > >
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.