>>>>That is weird, especially since SQL is supposed to open the tables separately.
>>>>
>>>>The only thing that comes to my mind is... if "OTHER" is a single-record table AND that record was created in the code right now AND you are using ROW buffering on the table, then the GO TOP would cause a TableUpdate(), making the record available in the second instance though not (yet) in the first.
>>>
>>>The Other table contains only one record but it was saved last night.
>>
>>Just curious... how does Other get to be at EOF() in that case?
>
>Well, nothing particular, that's the only place we use it in that application. However, doing GO TOP makes the SQL to work.

Well if it was saved last night AND it was NOT the subject to a REPLACE during this process, then I am at a loss.
I guess I am at a loss anyway, because IF it was saved last night then one would expect SQL to have given you the copy of the old record from disk EVEN IF you had done a REPLACE on the one in RAM.