Hi Michael -

On Mon, 16 Apr 2012 14:40:15 -0400, Michael Schutte
<mschutte369@xxxxxxxxx> 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?

I've been thinking along those same lines. We have prompt programs
for various fields: item number, brand number, supplier number,
customer number, salesperson number, etc. They are inconsistent in
the way the information is presented, and in many cases inconsistent
in how they even work.

So far I haven't actually done anything (because there aren't any new
prompt programs that we absolutely require and I've got too many high
priority projects to worry about prompt programs). Also, we have a
LOT of legacy RPGIII programs (including ones with program-described
WORKSTN files, oh joy!).

I haven't made a final decision, but I do like the idea of keeping
most or all of the prompting in one program, whether it be a service
program or an API-type *PGM.

Ken
Opinions expressed are my own and do not necessarily represent the views
of my employer or anyone in their right mind.

This thread ...


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].