×
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.
Hi Willie
Are you using RPG IV?
Well, you create ProgB with parameters that match the data types and
lengths of the screen fields in ProgA and then pass those values as
parms to ProgB when the user hits Enter - validate things as needed, of
course.
In a /copy member, put a prototype for ProgB and /copy that member in
ProgA. For ProgB I suggest using a prototype at the main level instead
of an *ENTRY PLIST.
Piece of cake! I hope!
If you have too many values for the number of parms you can use, maybe
put them into a data structure. Then pass that as one parm. You can have
arrays of values there, too.
Vern
Willie J. Moore wrote:
What I need to do is the following:
ProgA displays a screen for data entry, then calls ProgB passing the entered data as parms. ProgB then prints a report.
My problem is ProgA. I have the program display the entry screen. And I can call ProgB. But how do I set up the parms to pass through to ProgB?
Any help or examples would be appreciated.
Thanks,
William Moore
California Fine Wire
805-489-5144
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.