You are aware of AUTOADD [BEFORE] options? If you omit STRICT, LOOKUP uses SELECT ANYINPUT to wait for a record; when STRICT is specified, it does what it is documented to do.
On 07/15/2014 12:09 AM, Glenn Knickerbocker wrote: > I've never quite gotten this straight. In a LOOKUP feedback loop to add > or delete master records, the output record has to be buffered, since > the primary input hast to be released before it can be read on whichever > alternate input it's going to. For instance, to feed unmatched details > back in as new masters, COPY will hold the one record waiting to be > processed: > > (end /) ... | a: lookup ... / ... | a: | copy | ... | a: > > But is there some idiom to ensure the next detail record won't jump > ahead of this one? Or does LOOKUP try the alternate inputs first to > make sure that can't happen? > > ¬R >
