|
I remember that also. However, just because you put them into subroutines in order to go /free, doesn't preclude you from putting them in the physical order required by the precompiler. Rob Berendt -- "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." Benjamin Franklin rick.baird@xxxxxxxxxxxxxxx Sent by: rpg400-l-bounces@xxxxxxxxxxxx 08/18/2003 12:46 PM Please respond to RPG programming on the AS400 / iSeries To: RPG programming on the AS400 / iSeries <rpg400-l@xxxxxxxxxxxx> cc: Fax to: Subject: Re: SQLRPGLE with /FREE on a related note, it's been a while since I've used imbedded sql. I seem to remember that the precompiler had problems with the order in which it encounters SQL statements - in other words, it needed to see declare/open/fetch/close for instance in order within the source, or it would puke. is this still the case? If not (or even if so), would putting all of your sql statements in subroutines help the readability of mixing /free and +exec sql statements? - have all of your sql calls near the end of your source, all grouped together. Rick _______________________________________________ Just recently started coding in /FREE. Today, I'm writing in /FREE with SQL. Looking at some of the archives it seems that this may not be a good idea. What is the latest scoop on SQLRPGLE with /FREE? _______________________________________________ Richard Baird 317-655-7318 _______________________________________________ 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.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.