Yup. Use some given literal, like "While 1 < 2" (A Dennis McGrath tip) to establish each loop, set a var after each fetch "Set vYourVar = .SqlCode" and break out when appropriate.
Ben Petersen On 27 Sep 2002, at 12:46, J. Stephen Wills wrote: > I have a situation where, at least f/now, it seems best to CURSOR into > one table, then, f/ea record, CURSOR into another table f/matching > records. My problem is managing SQLCODE values. Is it possible to > use something other than ... > > WHILE SQLCODE <> 100 THEN > ... > ENDWHILE > > That is, could I set a variable equal to SQLCODE at the appropriate > points, such as after a FETCH, and test that variable? > > Thanks, > Steve in Memphis > > ================================================ > TO SEE MESSAGE POSTING GUIDELINES: > Send a plain text email to [EMAIL PROTECTED] > In the message body, put just two words: INTRO rbase-l > ================================================ > TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED] In > the message body, put just two words: UNSUBSCRIBE rbase-l > ================================================ TO SEARCH ARCHIVES: > http://www.mail-archive.com/rbase-l%40sonetmail.com/ > ================================================ TO SEE MESSAGE POSTING GUIDELINES: Send a plain text email to [EMAIL PROTECTED] In the message body, put just two words: INTRO rbase-l ================================================ TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED] In the message body, put just two words: UNSUBSCRIBE rbase-l ================================================ TO SEARCH ARCHIVES: http://www.mail-archive.com/rbase-l%40sonetmail.com/
