Filepro-list Digest, Vol 29, Issue 12

[Steve Bergman]

Boaz Bezborodko wrote:

>
>
> There are a number of things that could be happening here.  If he's 
> using a a GETNEXT opo within the loop then it will keep looking past 
> the matching records.  In other words, if you lookup "1234" then 
> GETNEXT will still bring you to "1235" and the "not opo" instruction 
> won't be met.  You will now go through all of "opo" before dropping 
> out of the loop for however many records opo has.  It will do this 
> every time it does this loop.  If this occurs in any other lookups as 
> well or opo is a very big file then you really are doing a lot of 
> unnecessary work.
>
> In FP there is also the option of defining a different (or no) 
> automatic processing when running a process.  The question is whether 
> you need to run the auto processing or not.  Or even if you need all 
> of it.  You can always copy the auto-processing file and modify the 
> copy with only what is needed for the report.
>
> Boaz

Thanks again.

So a lookup simply takes you to the first record that matches.  It does 
not return a result set, ala pgsql. (Duh!)

That's what I was missing.

-Steve