issues with called table causing lookup behaviour change...need help

[Kenneth Brody]

On 8/8/2013 6:00 PM, Fairlight wrote:
> I have a table sitting (with -sr 1) on a record, doing a lookup to another
> table.  I'm looping through all records in that table with a -ng lookup on
> an index.
[...]
> Here's the kicker.  During that -db trace, I found that the
> "not lookupname" is evaluating true after that one run past the table in
> question.  If I yank the call, it apparently must not be, as I get a second
> msgbox.  (There are currently only two records that would trigger the
> call/msgbox combination.)
>
> What about a call would cause the lookup to go screwy?  Is it because the
> records I'm looking through are the same table that the called table is
> altering?  It's not even altering the field upon which the index for the
> lookup in question is based.

Does the called table do a lookup to that same file, and CLOSE the lookup?

-- 
Kenneth Brody