Re: Prompt Service Program.

[Scott Klement <rpg400-l@xxxxxxxxxxxxxxxx>]

I'm not familiar with the term "prompt procedure."  What does it do?

Is this a routine called when a user hits F4=Prompt?  So all the screens 
that have F4=Prompt in all your application will call a procedure in the 
same service program (no matter what the underlying business logic or 
technical purpose may be?)

If so, I'd say that's a very strange way to divide up your work.


On 4/16/2012 1:40 PM, Michael Schutte wrote:
> 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?