|
>Essentially, the author was advocating using logical files with only thefields the application is using. This would enable you to add additional fields to the physical file without the need to recompile every logical>and associated programs.
The way to use this technique is to create application-specific logical files that have all the fields needed for the entire application, not just a single program. That way, you cut the number of LFs required to a smaller number. Of course, you need a complete set of LFs with all the varied key sequences the application requires.
Repeat the process for each application.For many applications this won't be much different than creating all those logical files-- except now the logical files list the fields that are visible to the application.
This is a long-advocated technique to allow selected users to update payroll records with name and address changes, without a chance of seeing the pay rate information-- the LF only includes the address info, and the user is not authorized to any LF that has pay information.
The maintenance headache comes when you have to add fields to the PF, and many of the LFs in an application need that field. You have to recompile the LFs and the programs that use them, or create a new batch of LFs (and the maintenance that adds).
--Paul E Musselman PaulMmn@xxxxxxxxxxxxxxxxxxxx
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
