>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.