|
In some cases a salesman has the authority to view several salesman numbers and their respective customer numbers. IE: WF has access to salesman 100, 110, 120, 200, and 300. On Tue, 29 Mar 2005 08:46:39 -0600, Bruce Guetzkow wrote > Doug: > > <snip> > I thought about creating a logical file for each salesman in customer > order > but maintenance would be heavy, as each time we add a new salesman I > have to > create a new logical file and then modify the code. > > I suppose I could create a logical joined file with the pertinent > info and then key in on the salesman and then customer, but I am not > sure if that is the best answer. > > I am open ears to anyone with any suggestions :) > </snip> > > Be careful what you ask for...you just might get it! ;-) > > I don't know the layout of your file, but I don't see why you'd need > to create a new logical every time you add a salesman. If the key > to the file is CUSTOMER/SALESMAN, then your data records could be > retrieved by doing a SETLL for the Customer/Salesman combination > specified and do a READE to retrieve ONLY the records for that > combination. If you want a different salesman, clear the subfile > and repeat the process with the new Customer/Salesman combo. One LF > should be all that you need. > > Am I missing something? > > --Bruce Guetzkow > > -- > This is the RPG programming on the AS400 / iSeries (RPG400-L) > mailing list To post a message email: RPG400-L@xxxxxxxxxxxx To > subscribe, unsubscribe, or change list options, visit: > http://lists.midrange.com/mailman/listinfo/rpg400-l or email: RPG400- > L-request@xxxxxxxxxxxx Before posting, please take a moment to > review the archives at http://archive.midrange.com/rpg400-l. -- Open WebMail Project (http://openwebmail.org)
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.