Actually I was just thinking the other day about how cool it would be if I
could "get at" that WCC and not have to use all these silly indicators...
especially in a maintenance program with lots of screen fields.
Thanks for bringing it up!
Karleen Bushard || IBM i Software Devloper || HOM Furniture, Inc ||
763.767.3777 || VM1777 || kbushard@xxxxxxxxxxxxxxxx
From: "sjl" <sjl_abc@xxxxxxxxxxx>
To: rpg400-l@xxxxxxxxxxxx,
Date: 09/27/2012 04:29 PM
Subject: Re: Using the same conditioning indicator
Sent by: rpg400-l-bounces@xxxxxxxxxxxx
Unfortunately, I had to resort to this technique with the JDE World Sales
order entry program (P4211) at my current client.
This program now has over 50,000 lines of code and long ago all of the
indicators got used up, so when making recent enhancements it was easier
to
use program-to-system fields to control the attributes of screen fields
rather than to save and restore indicators.
- sjl
wrote in message
news:mailman.3810.1348777198.2683.rpg400-l@xxxxxxxxxxxx..
.
WCC, write-control characters! flashback to CCP! (honk if you know
what I'm talking about)
Karleen Bushard || IBM i Software Devloper || HOM Furniture, Inc ||
763.767.3777 || VM1777 || kbushard@xxxxxxxxxxxxxxxx
From: "sjl" <sjl_abc@xxxxxxxxxxx>
To: rpg400-l@xxxxxxxxxxxx,
Date: 09/27/2012 02:55 PM
Subject: Re: Using the same conditioning indicator
Sent by: rpg400-l-bounces@xxxxxxxxxxxx
In lieu of indicators, program-to-system fields("P" fields) can be used to
control screen field colors and attributes...
http://www.itjungle.com/fhg/fhg101304-story01.html
- sjl
"Rpglist" wrote in message
news:mailman.3727.1348763689.2683.rpg400-l@xxxxxxxxxxxx...
Is there any issue with reusing a conditioning indicator that is on one
record format on another within the same display file? I'm out of
conditioning indicators
Sent from my iPhone=
midrange.com
