I have a client that has a rather large FoxPro for Windows 2.6 application that has been running well. Recently they acquired some Windows 2000 and Windows XP workstations.

When someone using a Windows 2000 /XP workstation logs in, it often reports that tables in the database are thrashed. The application automatically fixes these errors, but it has to have exclusive right to the files to repair the headers. However, when other people are logged in then they all have to log out first.

When someone is using Windows 98/ Windows ME, this does not happen. While the person running the application from Windows 2000 reports the files as damaged, the person running 98/ME simultaneously reports no problem.

Has anyone noticed this before? Any solution to the problem?

Help appreciated.

Steven