Thank you, Steve. I'll add RDocs9.5 to my wish list at work.
Patti
From: "[email protected]" <[email protected]>
To: RBASE-L Mailing List <[email protected]>
Sent: Monday, December 29, 2014 4:41 PM
Subject: [RBASE-L] - RE: - error code 406
Hi Patti,
Error codes are included in the RDocs9.5, which is well worth having if you
have not alreadypurchased it.
FWIW, the current 9.5 help file does not list SET POINTER in the help index (as
a subset ofthe SET command). Possibly error 406 is a legacy error code? Maybe
technically correct butreferring to a legacy description?
Steve
On 29 Dec 2014 at 18:45, Patti Jakusz wrote:
Hi Paul,I haven't used SET POINTER for at least 15 years. I didn't know it was
stillsupported. My code says DECLARE CURSOR. All other command filesI've
used lately work ok and end up getting error 100 when they run out ofrecords.
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 havealready been found, or no rows satisfy the condition of the SET
POINTERcommand. This condition sets the value of the variable specified in the
SETPOINTER and NEXT commands rather than the variable specified with the
SETERROR 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 SETPOINTER command. This condition sets the
value of the variable specified in theSET POINTER and NEXT commands rather than
the variable specified with theSET 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 thisprogram keeps running and running. I
figured out it gets an error code 406 when it runs out of records to read.
Idon't know where to find error code descriptions. Does anyone know whatthis
code means? Thanks,Patti Jakusz
