Paul,
Everything works fine when I test on my full Rbase, it started when I went
to the compiled apps at 3 different locations. Maybe it was just something
specific in my code, which I've changed from sqlcode and now it works. I just
don't know why all of a sudden after 2-3 years of the same code it happens now.
It is consistent. Three different locations, numerous computers, some XP.
some Windows 7
________________________________
From: Paul Buckley <[email protected]>
To: RBASE-L Mailing List <[email protected]>
Sent: Fri, May 14, 2010 8:12:50 AM
Subject: [RBASE-L] - Re: Scratch
Marc,
I have not stayed current on my 7.6 compiler, only 7.6 Rbase,
because I am migrating everything to eXtreme 9.0. However, I can tell you
that I have a 7.6 compiled application using version 7.6.8.31102 of the
compiler that checks the value of SQLCODE extensively and it works fine. Also,
the same code works fine in the latest version of the eXtreme 9.0 compiler
(which is generally the same as the other versions of compilers).
Hope this helps some.
Paul
From:[email protected]
[mailto:[email protected]] On Behalf Of MDRD
Sent: Friday, May 14, 2010 8:25 AM
To: RBASE-L Mailing List
Subject: [RBASE-L] - Re: Scratch
I
really hope this in not the case, I did a quick check and I use SQLCODE in over
50 places in my app.
Also,
I just updated all my users from 7.5 to 7.6.
Marc
From:TOM HART
Sent:Thursday, May 13,
2010 6:18 PM
To:RBASE-L Mailing List
Subject:[RBASE-L] - Re:
Scratch
It
appears that the sqlcode is not reliable on the new compiler 7.6 update.
I changed the code the err var and it worked. Now I need to go thru
and change all my codel
Tom Hart
________________________________
From:"[email protected]" <[email protected]>
To: RBASE-L Mailing List <[email protected]>
Sent: Thu, May 13, 2010 9:23:31 AM
Subject: [RBASE-L] - Re: Scratch
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
