>Today I got an error message from a customer: Cannot open a table, error # 1705. From what I know about the system, I doubt that another user had the table open exclusively.
>
>I have two questions:
>
>1. Is it possible that the error 1705 was caused by the table being updated by another user? (even though the other user opened the table in shared mode)

I don't think so but It could be cause by backup software or even ant-virus if it's to agressive.


>2. Do you recommend to enclose the USE command in a loop of a short time so that VFP has a chance to open the table, in case another user is updating it?

I would recomend to determine the cause of the problem and eleminate it.