My problems are always very elementary or very bizarre.
From: Dennis McGrath <[email protected]>
To: RBASE-L Mailing List <[email protected]>
Sent: Tuesday, December 30, 2014 12:03 PM
Subject: [RBASE-L] - RE: - error code 406
<!--#yiv9849878199 _filtered #yiv9849878199 {font-family:Helvetica;panose-1:2
11 6 4 2 2 2 2 2 4;} _filtered #yiv9849878199 {font-family:Helvetica;panose-1:2
11 6 4 2 2 2 2 2 4;} _filtered #yiv9849878199 {font-family:Calibri;panose-1:2
15 5 2 2 2 4 3 2 4;} _filtered #yiv9849878199 {font-family:Tahoma;panose-1:2 11
6 4 3 5 4 4 2 4;}#yiv9849878199 #yiv9849878199 p.yiv9849878199MsoNormal,
#yiv9849878199 li.yiv9849878199MsoNormal, #yiv9849878199
div.yiv9849878199MsoNormal
{margin:0in;margin-bottom:.0001pt;font-size:12.0pt;font-family:"Times New
Roman", "serif";}#yiv9849878199 a:link, #yiv9849878199
span.yiv9849878199MsoHyperlink
{color:blue;text-decoration:underline;}#yiv9849878199 a:visited, #yiv9849878199
span.yiv9849878199MsoHyperlinkFollowed
{color:purple;text-decoration:underline;}#yiv9849878199
p.yiv9849878199MsoAcetate, #yiv9849878199 li.yiv9849878199MsoAcetate,
#yiv9849878199 div.yiv9849878199MsoAcetate
{margin:0in;margin-bottom:.0001pt;font-size:8.0pt;font-family:"Tahoma",
"sans-serif";}#yiv9849878199 span.yiv9849878199BalloonTextChar
{font-family:"Tahoma", "sans-serif";}#yiv9849878199
span.yiv9849878199EmailStyle19 {font-family:"Calibri",
"sans-serif";color:#1F497D;}#yiv9849878199 .yiv9849878199MsoChpDefault
{font-size:10.0pt;} _filtered #yiv9849878199 {margin:1.0in 1.0in 1.0in
1.0in;}#yiv9849878199 div.yiv9849878199WordSection1 {}-->In any case, you
should not be getting an SQLCODE of 406 when your FETCH encounters end of data,
you should always get 100. Dennis McGrath From: [email protected]
[mailto:[email protected]] On Behalf Of Patti Jakusz
Sent: Tuesday, December 30, 2014 11:00 AM
To: RBASE-L Mailing List
Subject: [RBASE-L] - RE: - error code 406 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 already purchased
it. FWIW, the current 9.5 help file does not list SET POINTER in the help
index (as a subset of the SET command). Possibly error 406 is a legacy error
code? Maybe technically correct but referring 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 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
