|
The functions are the same; only the data is different. I have 649 individual "tables" I can look up with a single function (the "LOOKUP" program); this is part of my on-line help system. All the entries are in a single PF and the function works exactly the same way regardless of the "table" (subset) used. When my customer see this: "Terms? . : _____' they know they can place a "?" in the first position, press ENTER, and get a window with all the valid values. They could use the "?" in the currency field, or the shipment type field, or the package code field: it all works the same way, and I don't think that writing 648 programs (or having an additional 648 tables) is smart. The single PF (composite key, of course) is used for editing; I have a procedure set up to handle value validation. The end result is a simple, extremely robust system. -reeve -----Original Message----- From: rpg400-l-admin@midrange.com [mailto:rpg400-l-admin@midrange.com]On Behalf Of James Rich Sent: Thursday, October 31, 2002 2:03 PM To: rpg400-l@midrange.com Subject: Re: Prototypes and parameters On Thu, 31 Oct 2002 bill.reger@convergys.com wrote: > Make them two different functions, since they perform different activities. I second this suggestion. If the two functions end up having a lot similarities you could create a third function of the common code. But in general I believe you should one function that does one thing. James Rich _______________________________________________ This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list To post a message email: RPG400-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/rpg400-l or email: RPG400-L-request@midrange.com Before posting, please take a moment to review the archives at http://archive.midrange.com/rpg400-l.
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.