|
Dean Asmussen (DAsmussen@aol.com) wrote: >Fine, but why create a new logical (and it's inherent overhead) when you >already have one in place to perform the desired function? The scheme simply gives you the freedom to make the decision whether it's justified or not. You may want to create the new logical for expediency and then at a later date incorporate the new field(s) into an existing logical and retire the new one. You have the overhead of an extra logical but you also have full database integrity. You might also want to use it where the new fields applied only to a limited set of functions. Only the programs used in those functions need to see the new fields therefore the new logical is justified. All programs are built over logical files containing just the fields relevant to their function. Dave Kahn - TCO, Tengiz, Kazakstan ========= e-mail: kahn@tengizchevroil.com (until September 30th) dkahn@cix.compulink.co.uk (from October 1st) +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to "MIDRANGE-L@midrange.com". | To unsubscribe from this list send email to MAJORDOMO@midrange.com | and specify 'unsubscribe MIDRANGE-L' in the body of your message. | 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.