Are you talking about a prompt being something like a user is on a screen in an 'action' field and they want to press F4 to see the values (and select one)?

A quick brainstorm on the topic:
Program calls service program procedure to bring up a prompt window. Pass in the program name, screen name, and field name.
Service program will reference a table where you have all of the possible prompt values stored along with their descriptions (A , Add; D, Delete; etc).
Service program pops up a window (or screen, whatever) for user to select from the options.
Service program procedure returns the selected value. To prepare to handle most situations, you could return an 80a field and if you're on IBM i 7.1 you can code RTNPARM on the Procedure Interface so it returns the selection by reference.

If this method would work, there's really no growth for added prompts since they'd all be stored in a table. That table might look like this:
Header table:
Program
Screen
Field
Header1a
Header1b (in case you want to stack header descriptions to save on horizontal space)
Header2a
Header2b (in case you want to stack header descriptions to save on horizontal space)
Max Value Length

Detail Table
Program
Screen
FieldValue
Description

The service program could then dynamically build the screen. I think I did something like this a long time ago and at that time I made the value max size 20 and then the description a certain size so the only dynamic part was the wording that appeared on the screen (not the actual positions of values).

-Kurt

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Michael Schutte
Sent: Monday, April 16, 2012 1:40 PM
To: RPG programming on the IBM i / System i
Subject: Prompt Service Program.

Would any advise for or against putting any new prompt procedures in the same service program? Just curious. I started a new service program with the intent to put any new prompt programs in this service program. But then I got to thinking maybe that would be a bad idea because as the size of the service program grew, so would the amount of memory each time the program was activated. I am using a named activation group.

Anyway, am I off on trying to create just one service program for any prompt-able field?
--
This is the RPG programming on the IBM i / System i (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.


This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 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].