>>When error 1707 occurs, does Fox 2.6 generate the error and remove the reference from the table???? That would explain why my second user's attempts would work. And also why this error trap merely retries the USE.
>
>Yes, though (don't remember the details) it may depend on your Set Safety and Set Notify. The reason I don't remember this was because I haven't seen the message for quite a number of years, because my indexing routines have removed the reference from the table, deleted the cdxes, and created new ones automatically. The reference is a 1 in 28th byte of the table header, and gets removed with writing a zero there.
>


Dragan:

Thanks for the info. On my machine SET SAFETY ON generated the error, while SET SAFETY OFF just removed the reference. OTOH, the error dump from my user indicates that Safety was OFF, but they still got the message.

Between your info and the link Sergey pointed me too, I should be able to get them by the error screen and have them up and running properly.

Thanks to both of you.

..........Rich