|
I've actually seen canned packages do something like this. The problem is when they change field sizes. And, yes, I've seen other canned packages do this also. Even on the primary key to their item master. I suppose your business may decide to not take advantage of the new field sizes (you can only use the first x characters of fielda), but after awhile that raises the bile in your throat. Rob Berendt -- Group Dekko Services, LLC Dept 01.073 PO Box 2000 Dock 108 6928N 400E Kendallville, IN 46755 http://www.dekko.com William Washington III <w.washington3@xxxxxxxxxxxxx> Sent by: midrange-l-bounces@xxxxxxxxxxxx 03/08/2005 09:09 PM Please respond to Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> To midrange-l@xxxxxxxxxxxx cc Subject RE: Logical File or OPNQRYF or any other way ? - Legacy Hey! Now THAT is kewl! Seriously! And it makes perfect sense, because the view has all of the info that particular program needs. Another program would use a different view. I see no need to ever change a particular view, unless, once again, someone went to extremes with creating them. I'll put that info to use immediately! Thanks, Chris. William > date: Tue, 8 Mar 2005 15:19:07 -0800 > from: Chris Bipes <chris.bipes@xxxxxxxxxxxxxxx> > subject: RE: Logical File or OPNQRYF or any other way ? - Legacy > > 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? > > -- This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-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.