×
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.
Well in your original code you were EVALing individual fields - I was
just pointing out that there was a simpler way.
If globals works for you then you have a scenario where qualified DS
are not needed anyway.
I don't see why you have to do it every time - that doesn't make
sense. You do it as and when you need to update/write to a specific
file and you do it just before the output.
You say that global also presents problems - what are they?
We could offer better suggestions if you told us the design issue you
are facing rather than showing us code. If we know what and why you
are trying to achieve we may be able to offer a more satisfactory
alternative.
Jon Paris
www.Partner400.com
www.SystemiDeveloper.com
On Aug 17, 2010, at 1:00 PM, rpg400-l-request@xxxxxxxxxxxx wrote:
Well, Jon, There lies the problem: To do what you suggested, that
means
each time the program performs chain/update/write/read, I've to do
remember to do eval-corr to make sure all version of qualified DS
contains the same data. The best choice seems to be to not use
result-field DS (fall back to global). But this has its own problem
also.
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
