|
Uh, we do. I might stick to that, but you'll probably reply 'Why?' (maybe with more than one question mark), so I'll try to answer that obvious question as well. Because: 1. We like to see in the source which fields we actually use 2. We don't like having hundreds of fields from a file in a program, when we only need a description. And no, we don't want an extra logical just for the description, and another one for the description and the price, and another one ... And we don't like the risk of having fields overwritten by reading another file that happens to have that same field. 3. We always have a library list which contains one or more base applications as well as customer modifications. Most of the times these modifications need extra fields in the data base, which would imply (when using externally described files in RPG) either having a version of the base application(s) compiled against the modified data base, or having separate logicals for the base record layout and the extended layout. But rest assured, we don't manually type in record layouts: we have our own data base tool that generates (amongst others) the record layouts and is able to adjust the RPG-specifications. Joep Beckeringh ----- Original Message ----- From: "Jim Langston" <jlangston@conexfreight.com> To: <RPG400-L@midrange.com> Sent: Tuesday, April 25, 2000 8:08 PM Subject: Re: DOU/DOW for READ Loops > Oh, yes, I just hate KLists. And you can't use a data structure in a KList. > > This defininately should be changed. Even in S36 you could use a data > structure for a key field, since the file was internally described. I guess you > could internally describe the file in RPG IV, but who would want to? > > Regards, > > Jim Langston > > Bald mans lament: Hair today, gone tomorrow. +--- | This is the RPG/400 Mailing List! | To submit a new message, send your mail to RPG400-L@midrange.com. | To subscribe to this list send email to RPG400-L-SUB@midrange.com. | To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.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.