×
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.
Hello Jerry
Am 27.11.2024 um 14:34 schrieb (WalzCraft) Jerry Forss <JForss@xxxxxxxxxxxxx>:
I have had better luck changing the subfile field to a char that is 1 longer than the display size. A 7.2 Amt with a J code would be 10 + 1=11
In the pgm if you want red I do a AmtOut = HexRed + %EditC(Amt : 'J')
HexRed is x'28', HexWhite is x'22' and hexgreen is x'20'
This sounds a bad hack and I strongly discourage from using such a workaround. Indicators and COLOR() are there for a reason.
I have had issues with losing the indicator value when the record is read.
Can't duplicate. But then, I don't care, have never cared, about READing indicators from SFL records.
I'm always using a SR which is called prior to the SFL WRITE, handling every variable and probably differently named target (DSPF) variables. This is also called upon UPDATE of an SFL record, to eliminate the less efficient re-read the whole SFL needlessly after a change in one record. I handle SFL functions like color of a record derived from a variable in this SR, and if the color is determined by a variable not in the SFL, I add this variable as a hidden SFL field so it's always there with the correct value.
:wq! PoC
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.
midrange.com
