×
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.
On 2013-01-22, at 11:56 AM, rpg400-l-request@xxxxxxxxxxxx wrote:
In short folks, it didn't work. Debugging the statement shows the following:
General Indicators:
... 30 '1' 31 '1' 32 '1' ...
Before the %subarr statement, they were all '0'.
So, I'm back to the drawing board but needed to inform the list so someone
else doesn't try the same thing!
It is doing exactly what I would expect.
You can't use %SubArr for this - all it does is narrow the range of elements being considered. It doesn't change the behaviour.
I could have sworn that in the article you were referenced to - or in a post here - I described the only way I know to make it work - assuming you still need individual access to 30, 31, and 32 is to use a group field in the DS.
D indicators DS ....
D myGroup Overlay(indicators: 30)
D nameFor30 n Overlay(myGroup)
D nameFor31 n Overlay(myGroup: *next)
D nameFor32 n Overlay(myGroup: *next)
myGroup = '101';
Jon Paris
www.partner400.com
www.SystemiDeveloper.com
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
