×
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.
Peter Vidal wrote:
"Select;
When RunQtr = 1;
Update MPSSumR %fields(MPBQ1);
When RunQtr=2;
Update MPSSumR %fields(MPBQ2);
...
or
Update MPSSumR %fields(MPBQ1:MPBQ2:MPBQ3:MPBQ4);
or
Update MPSSumR;
I am guessing at MPBQ1. This email is so cleaned up I can't see the
original file field names used in the array."
Rob, you are using the correct names and any of these options may work. What
confuses me is the fact that apparently %FIELDS can't handle arrays.
Is this true?
As someone else pointed out, %FIELDS doesn't handle arrays simply
because the OS/400 database doesn't support arrays. The compiler needs
to know *which* database field to update. If there isn't a direct
relationship between the name specified in the %FIELDS list and the
database record, the compiler can't make any assumptions. If some field
happens to overlay some database field, well, that just isn't quite good
enough.
Note that the field specified in the %FIELDS list may also be a subfield
of a LIKEREC data structure, in which case there is a clear
relationship, and the compiler can figure out which field in the record
to update.
Cheers! Hans
As an Amazon Associate we earn from qualifying purchases.
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.