× 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.



we are having a debate here about files with composite keys, and how SETLL and READE will position...

example:
File 1 key: Order#, Operation#

File 2 key: Order#, Sequence#

however, when I code my loop, I want to read all file 1 records for that order, and within that loop I want to read all file 2 records.

we have it coded as:
<<<ORDER# is a field, not a KLIST>>>

ORDER# SETLL File1
ORDER# READE File1
DOU %eof(FILE1)
... ...
ORDER# SETLL File2
ORDER# READE FILE2
DOU %eof(file2)
... ...
ENDDO
ENDDO
HERE IS OUR DEBATE POINT:

some of us are remembering problems with not setting ALL KEY VALUES, because you may have problems with the remaining key fields not being
set to *LOVAL...
However, I seem to think that was only when you were using a KLIST or something like that...


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.