|
Hi Mark, From: <MWalter@hanoverwire.com> > Regardless of your choice of I/O, you still have to handle the data > properly. The AS/400 supplies the record format level id that helps you in > this. > In using SQL, by selecting only the columns that I need, if the underlying > database structure changes, unless a change is made to one of the columns > selected, I don't need to recompile. Yes, but if you're using SQL, and a change *is* made to one of the columns (e.g. changing character to packed-decimal without changing the field name, or changing the length of a field), you have no warning, although you *might* get a run-time error, since (as you can see from a compiled SQLRPGLE listing) your program is actually doing EVAL's to move data, and EVAL's will not convert character-to-numeric or vice versa as MOVE does. With native I/O, you'd get a CPF4131 level-check error when the file is being opened. Raise your hand if you've seen more than one report with 404040.40 in a money field<G>. Regards, Peter Dow Dow Software Services, Inc. 909 425-0194 voice 909 425-0196 fax _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com
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.