>Are you sure that the row in other has been committed? It sounds like your GO TOP is causing that to happen.
This is from a robot application that no data entry is in effect. The save of that record was done 24 hours ago and restarting the robot was generating no record from that 2nd part of the UNION. So, I had to force a GO TOP. I just thought about that just in case a bug would be in effect assuming only one record in the 2nd UNION or similar.