No the table was not corrupt. As I said, I made a copy and opened it and inspected it. It was not corrupt. Foxpro was able to open the copy just fine.

I rebooted the fileserver and the issue is fixed for now. I treated the symptom, but have no idea of the cause. Before I rebooted the server, I went around to every client and rebooted each one. That did not have an affect either.

I have seen exactly the same behaviour when a client has a file open and gets an error. If the user leaves the error on the screen, then the file is left open and no one else on the network can access it. That is why I went around and checked all my clients. Something had that file open and wouldn't let it go, at least that is my gut feeling.

Sorry I could no longer wait for rebooting. Business must go on...

This happened friday evening, now again today.