×
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.
The example I did for my last application was that I have multiple ways to
display or access the data and didn't want to write the business rules
multiple times for each file update. So I have one program that focuses on
updating the tables, and one program that focuses on displaying the data. In
my case, for each set of master/comment files. Then I wrote subfile display
programs to used for selection and called the proper update/display program.
This really was smart of me during to do this when I rewrote everything,
because a couple weeks later more business rules where added and I didn't
have to change 10 programs to include the same logic for each.
On Oct 31, 2007 1:19 PM, Scott Klement <rpg400-l@xxxxxxxxxxxxxxxx> wrote:
This is an interesting thread. I've never hard of this "one screen /
one module" recommendation before. I'm having a hard time understanding
why you'd do this...
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
