×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
Mike Cunningham wrote:
We have 100 LFs built over the same PF each with the same
key field list. There is only one access path shared by all 100
LFs and each LF only uses the fields the app needs. In essence
each application has its own view of the database much like an
SQL select that list only the fields the application needs.
A colleage of mine who has done a lot of consulting for many years
explained this technique to me, and I was intrigued with it when I heard
it, and it's nice for you to share your experience with it. It does
indeed seem ahead of its time. SQL views are another nice derivative of
the idea.
It seems to me that this idea would work well in a setting where you're
doing a lot of customization over a vendor's database. The vendor may
add new fields, which may force them to recompile a lot of their
programs, but it wouldn't have much if any impact to your programs.
Nathan.
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.