I just checked the link and the entire compilation listing *not* included. However, when I pasted it (and before pushing the "Add Entry" button), I checked and the entire thing *was* there. This may be a limitation of the Code stuff. Huh, David?
Jerry C. Adams
IBM System i Programmer/Analyst
--
B&W Wholesale
office: 615-995-7024
email: jerry@xxxxxxxxxxxxxxx
-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Jerry Adams
Sent: Monday, September 21, 2009 1:49 PM
To: RPG programming on the IBM i / System i
Subject: RE: SQL Pre-compiler Fields Names Undefined
Sorry about that; don't know what happened. I confirmed this time (
http://code.midrange.com/2007d2aa1e.html) that the end of compile message got posted to the code site member.
SQLString is used in the $BuildList subprocedure. And, indeed, it (sqlstring) is simply used to retrieve records from a sequential file and to order them based upon a panel option. The cursor, too, is declared in the $BuildList procedure.
Jerry C. Adams
IBM System i Programmer/Analyst
--
B&W Wholesale
office: 615-995-7024
email: jerry@xxxxxxxxxxxxxxx
-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Monday, September 21, 2009 1:28 PM
To: RPG programming on the IBM i / System i
Subject: RE: SQL Pre-compiler Fields Names Undefined
1 - It's missing data at the bottom, which is often useful on a compile
listing. ;-)
2 - The source file rather confirms that it was sql
# Source File . . . . . . . . . . : QSQLTEMP1
# Library . . . . . . . . . . . : QTEMP
I don't see where sqlString is used. I can see where it is built. I
don't see it put into a cursor. And since it doesn't use a SELECT INTO
but just a plain SELECT it has to go into a cursor, right?
Rob Berendt
midrange.com
