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