|
If they get a new iSeries and the Enterprise Edition then they get the license for that. Rob Berendt -- "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." Benjamin Franklin Scott Klement <klemscot@xxxxxxxxxxxx> Sent by: rpg400-l-bounces+rob=dekko.com@xxxxxxxxxxxx 11/18/2003 02:16 PM Please respond to RPG programming on the AS400 / iSeries <rpg400-l@xxxxxxxxxxxx> To RPG programming on the AS400 / iSeries <rpg400-l@xxxxxxxxxxxx> cc Subject RE: RPG IV release levels and complexity On Tue, 18 Nov 2003, Bob cozzi wrote: > Here's a posting from another list that typifies why /FREE can be ugly (as > can fixed-format). If both /free and fixed format are ugly (which is exactly what you've said) then what good does it do to stay with fixed format? My experience has been that things get ugly whenever you switch back and forth between fixed-format and /free. I try to never mix /free and fixed in the same subprocedure. If I *must* have fixed for some reason (which I'm not sure I've even run into yet) I put it into it's own subprocedure. Of course, I don't use SQL, which might be part of the reason I don't see the disadvantage. I should really learn SQL, it would probably make me a better programmer. But, I haven't yet seen a need for it -- and the company I work for does not own the licpgm... _______________________________________________ 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.