That made the difference.  Now I got error 100.  I wonder why it worked almost 
all the other times I ran programs using error variables instead.
Thank you everyone.Patti

      From: Patti Jakusz <[email protected]>
 To: "[email protected]" <[email protected]> 
 Sent: Tuesday, December 30, 2014 6:50 PM
 Subject: Re: [RBASE-L] - RE: - error code 406
   
Hi Dennis,Sorry I missed this.  It slipped into my spam folder.
I will try SQLCODE instead and let you know how it goes.
Patti

      From: Dennis McGrath <[email protected]>
 To: RBASE-L Mailing List <[email protected]> 
 Sent: Tuesday, December 30, 2014 12:27 PM
 Subject: [RBASE-L] - RE: - error code 406
   
#yiv7628291469 #yiv7628291469 -- filtered {font-family:Helvetica;panose-1:2 11 
6 4 2 2 2 2 2 4;}#yiv7628291469 filtered {font-family:Helvetica;panose-1:2 11 6 
4 2 2 2 2 2 4;}#yiv7628291469 filtered {font-family:Calibri;panose-1:2 15 5 2 2 
2 4 3 2 4;}#yiv7628291469 filtered {font-family:Tahoma;panose-1:2 11 6 4 3 5 4 
4 2 4;}#yiv7628291469 p.yiv7628291469MsoNormal, #yiv7628291469 
li.yiv7628291469MsoNormal, #yiv7628291469 div.yiv7628291469MsoNormal 
{margin:0in;margin-bottom:.0001pt;font-size:12.0pt;}#yiv7628291469 a:link, 
#yiv7628291469 span.yiv7628291469MsoHyperlink 
{color:blue;text-decoration:underline;}#yiv7628291469 a:visited, #yiv7628291469 
span.yiv7628291469MsoHyperlinkFollowed 
{color:purple;text-decoration:underline;}#yiv7628291469 
p.yiv7628291469MsoAcetate, #yiv7628291469 li.yiv7628291469MsoAcetate, 
#yiv7628291469 div.yiv7628291469MsoAcetate 
{margin:0in;margin-bottom:.0001pt;font-size:8.0pt;}#yiv7628291469 
p.yiv7628291469msonormal, #yiv7628291469 li.yiv7628291469msonormal, 
#yiv7628291469 div.yiv7628291469msonormal 
{margin-right:0in;margin-left:0in;font-size:12.0pt;}#yiv7628291469 
p.yiv7628291469msochpdefault, #yiv7628291469 li.yiv7628291469msochpdefault, 
#yiv7628291469 div.yiv7628291469msochpdefault 
{margin-right:0in;margin-left:0in;font-size:12.0pt;}#yiv7628291469 
span.yiv7628291469msohyperlink {}#yiv7628291469 
span.yiv7628291469msohyperlinkfollowed {}#yiv7628291469 
span.yiv7628291469emailstyle17 {}#yiv7628291469 p.yiv7628291469msonormal1, 
#yiv7628291469 li.yiv7628291469msonormal1, #yiv7628291469 
div.yiv7628291469msonormal1 
{margin:0in;margin-bottom:.0001pt;font-size:12.0pt;}#yiv7628291469 
span.yiv7628291469msohyperlink1 
{color:blue;text-decoration:underline;}#yiv7628291469 
span.yiv7628291469msohyperlinkfollowed1 
{color:purple;text-decoration:underline;}#yiv7628291469 
span.yiv7628291469emailstyle171 {color:#1F497D;}#yiv7628291469 
p.yiv7628291469msochpdefault1, #yiv7628291469 li.yiv7628291469msochpdefault1, 
#yiv7628291469 div.yiv7628291469msochpdefault1 
{margin-right:0in;margin-left:0in;font-size:10.0pt;}#yiv7628291469 
span.yiv7628291469EmailStyle27 {color:#1F497D;}#yiv7628291469 
span.yiv7628291469BalloonTextChar {}#yiv7628291469 .yiv7628291469MsoChpDefault 
{font-size:10.0pt;}#yiv7628291469 filtered {margin:1.0in 1.0in 1.0in 
1.0in;}#yiv7628291469 div.yiv7628291469WordSection1 {}#yiv7628291469 Patti  
Review the docs for this  You should be checking SQLCODE  open cursorfetch 
statement  while SQLCODE <> 100 then   misc processing   fetch 
statementendwhile      From: [email protected] [mailto:[email protected]] On 
Behalf Of Patti Jakusz
Sent: Tuesday, December 30, 2014 11:12 AM
To: RBASE-L Mailing List
Subject: [RBASE-L] - RE: - error code 406  Hi Javier,

Every time I declare a cursor, I use the same format:  drop cursor, if it's open

set error variable vErrCodedeclare cursor statement

open cursorfetch statementset vSaveErr=.vErrCode

while vSaveErr <> 100 then   misc processing   fetch statement   set 
vSaveErr=.vErrCodeendwhile

This has always worked before.  But the command files never stopped.  I had to 
use Task Mgr to end it.  So I traced it with only 2 records to process so I 
could see what the error was.  And it said error 406, instead of the 
anticipated 100.

PattiFrom: Javier Valencia <[email protected]>
To: RBASE-L Mailing List <[email protected]> 
Sent: Monday, December 29, 2014 4:49 PM
Subject: [RBASE-L] - RE: - error code 406  Patti,The location of the command 
where you check the code is critical since any other command(s) you run before 
it can reset the code. Maybe if you post the code in the loop and after the 
Declare Cursor, it would debugging your issue.  Javier,    From my Android 
phone on T-Mobile. The first nationwide 4G network.


-------- Original message --------
From: Patti Jakusz <[email protected]> 
Date: 12/29/2014 12:45 PM (GMT-06:00) 
To: [email protected] 
Subject: [RBASE-L] - RE: - error code 406 

Hi Paul,I haven't used SET POINTER for at least 15 years.  I didn't know it was 
still supported.  My code says DECLARE CURSOR.   All other command files I've 
used lately work ok and end up getting error 100 when they run out of records.  
I don't even understand what happened here.    My problems always seem so 
bizarre.    Patti  

From: Paul Buckley <[email protected]>
To: RBASE-L Mailing List <[email protected]> 
Sent: Sunday, December 28, 2014 6:40 PM
Subject: [RBASE-L] - RE: - error code 406  Patti, You are using a pointer to 
access rows of data in a table. Either all rows have already been found, or no 
rows satisfy the condition of the SET POINTER command. This condition sets the 
value of the variable specified in the SET POINTER and NEXT commands rather 
than the variable specified with the SET ERROR VARIABLE command. According to 
R:DOCS; You are using a pointer to access rows of data in a table. Either all 
rows have already been found, or no rows satisfy the condition of the SET 
POINTER command. This condition sets the value of the variable specified in the 
SET POINTER and NEXT commands rather than the variable specified with the SET 
ERROR VARIABLE command. Paul Buckley From: [email protected] 
[mailto:[email protected]] On Behalf Of Patti Jakusz
Sent: Sunday, December 28, 2014 5:41 PM
To: RBASE-L Mailing List
Subject: [RBASE-L] - error code 406 Hello, I'm writing a command file with a 
declared cursor.  I check, as I always do, for error code 100 to indicate I've 
come to the end of my records.  But this program keeps running and running.  I 
figured out it gets an error code 406 when it runs out of records to read.  I 
don't know where to find error code descriptions.  Does anyone know what this 
code means? Thanks,Patti Jakusz    

   

  

Reply via email to