Patti Review the docs for this
You should be checking SQLCODE open cursor fetch statement while SQLCODE <> 100 then misc processing fetch statement endwhile 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 vErrCode declare cursor statement open cursor fetch statement set vSaveErr=.vErrCode while vSaveErr <> 100 then misc processing fetch statement set vSaveErr=.vErrCode endwhile 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. Patti ________________________________ From: Javier Valencia <[email protected]<mailto:[email protected]>> To: RBASE-L Mailing List <[email protected]<mailto:[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]<mailto:[email protected]>> Date: 12/29/2014 12:45 PM (GMT-06:00) To: [email protected]<mailto:[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]<mailto:[email protected]>> To: RBASE-L Mailing List <[email protected]<mailto:[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]> [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
