|
Actually if you create views to use with your RPG program that do not share the view of the PF, you can add or move fields in the PF and not effect any RPG programs using the other views. Now if you remove a field used by SQL or RPG you will have problems until you update your programs not to use that field. It will also cause problems with your defined views. Think of a LF that has it's own record format, not using the PF record format as a view. Now how does that differ from imbedded SQL except in flexibility of creating the view on the fly. Chris Bipes -----Original Message----- If I make a change to the database, yes, I will have to modify (typically, recompile) my RPG programs. So what? That's part of the process. The fact that the database is bound to the program gives RPG its well-deserved reputation for random-access performance. That is the design tradeoff for a business machine. If the data layouts are changing all the time, well, what kind of model is the business operation on?
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.
midrange.com
