|
> > If no matching record specified, (each) secondary file is read (in turn) > after the primary file is completely read. Unless you override this behavior with the NEXT opcode, instructing the cycle to read from a given primary or secondary on the next cycle. This feature was most often used when you wanted explicit control of the "interlacing" of the files when matching records couldn't be used. It was generally used in conjunction with look-ahead fields to decide what record you wanted to read next. Back in the days of card readers, it could be useful. :) Doug
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.