RE: SQLRPGLE won't compile...

>> It must precede any other SQL statements.
Not true.  

I place my set options in the *INZSR and its at the bottom of all other
subroutines (source sequence wise).  The SQL PREPARE and DECLARE all must
occur source sequence wise before any other use.  

A WDSC filtered view of the SQL statement in source sequence;
     C+ PREPARE SQLST FROM :SQLSTMT
     C+ DECLARE SQLCSR SCROLL CURSOR FOR SQLST
     C+ FETCH RELATIVE :PUROWS FROM SQLCSR
     C+ FETCH BEFORE FROM SQLCSR
     C+ FETCH RELATIVE :purows FROM SQLCSR
     C+ FETCH NEXT FROM SQLCSR FOR 1 ROWS INTO :RSDATA
     C+ FETCH NEXT FROM SQLCSR
     C+ FETCH AFTER FROM SQLCSR
     C+ FETCH PRIOR FROM SQLCSR
     C+ CLOSE SQLCSR
     C+ OPEN SQLCSR
     C+ FETCH BEFORE FROM SQLCSR
     C+ SET OPTION DATFMT = *USA
     C+   ,ALWCPYDTA = *NO
     C+   ,CLOSQLCSR = *ENDMOD
     C+   ,DLYPRP = *YES         


Thank you,
Matt Tyler
WinCo Foods, LLC
mattt@xxxxxxxxxxxxxx


-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx]
On Behalf Of Gina M Whitney
Sent: Wednesday, April 06, 2005 9:09 a
To: rpg400-l@xxxxxxxxxxxx
Subject: RE: SQLRPGLE won't compile...

>> Second, the SET OPTION statement can be about anywhere.

It must precede any other SQL statements.





-- 

This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.