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.

good luck


>I just found something weird that I am looking to get some additional information on. It is in regards to a UNION clause where, being executed from the command prompt works, but, when being executed from the code, if the cursor of the UNION table is at EOF(), does not grab the related record.
>
>For example:
>
>

>SELECT Member.FName,Member.LName,Member.Numero FROM Reservation;
> INNER JOIN Member ON Reservation.NoMember=Member.Numero;
> UNION;
>SELECT Member.FName,Member.LName,Member.Numero FROM Other;
> INNER JOIN Member ON Other.NoMember=Member.Numero;
> ORDER BY LName INTO CURSOR Temp
>

>
>if executed from the code, doesn't grab the specific record from the Other table. However, doing this will make it work:
>
>

>SELECT Other
>GO TOP
>SELECT Member.FName,Member.LName,Member.Numero FROM Reservation;
> INNER JOIN Member ON Reservation.NoMember=Member.Numero;
> UNION;
>SELECT Member.FName,Member.LName,Member.Numero FROM Other;
> INNER JOIN Member ON Other.NoMember=Member.Numero;
> ORDER BY LName INTO CURSOR Temp
>

>
>What is causing such reaction?