SQLCODE has a very simple definition in the ANSI SQL Standard, from back in the 2.11 days: Zero means the command completed normally, 100 means no rows found, and all other values are implementation dependent negative numbers. R:BASE made it minus one times the R:BASE Error value.
Bill On Thu, May 13, 2010 at 10:23 AM, <[email protected]> wrote: > Tom: I can't tell you why I made this decision, but there is only > one place in all my program code all over this country going back to > 2.11 days where I use the SQLCODE command. The only place I > use sqlcode is within a cursor: > fetch c1 into vproductid > if sqlcode = 100 then > break > endif > > I never use sqlcode anywhere else for testing. I guess I didn't > trust that the same command would "break" a sqlcode reliably > from version to version.... But as I said, personal choice and I > can't comment on whether it's a good idea to use sqlcode or not... > > Karen > > > > First off I want to thank Razz, Rachael, and Albert for their help. I did > get it to work right. Now I have a question, what happened from the last 2 > compiler builds. This code I posted I have been using for at least 2 years, > at 3 locations, and on more than 10 computers and have never once had this > happen. Is it better to use the code you posted and/or is the sqlcode > becoming obsolete. I am sure I have sqlcode elsewhere in my app, but > obviously employees clock in and out everyday, so it came up first. I have > not changed the code or form at all, just re-compiled my startup file with > the newer compiler version. > Tom Hart > > >
