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

Fairlight fairlite at fairlite.com
Thu Aug 8 15:00:44 PDT 2013


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.

I have values being grabbed from each record, and then I call another
processing table, and throw up a msgbox.

If I comment out the call, I get a msgbox for each record that should be
affected.  

If I put the call back in, only the first match ever presents a msgbox, and
processing seems to end.

The called table is using 'end', but that should only end -that called
table-, not all of processing, right?  Right.  I just verified that known
behaviour with -db.

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.

mark->
-- 
Audio panton, cogito singularis.


More information about the Filepro-list mailing list