I was having the same problem, and upgraded to a Win2000 server. That solved the "Not a database" error on the XP machines, but I was also running and end of month process from a DOS machine that I upgraded to a Win98 machine at the same time, and the run time of that process went up dramatically (from about 10 minutes to around an hour). I still haven't solved that problem.

June

>We have a 20+ node Foxpro application which until lately has been run on WIN98 computers. The file server is still win98.
>
>Now, if someone on a Win98 computer keeps a data entry screen open (with direct "get" commands to the table field)and an XP computer tries to load the application we get a "Not a database" error on the XP. Other Win98 computers have no problem to start the application.
>
>When the computer with the data entry screen gets out, the XP can load without any problems. If I run DSalvage on the table in question, there are no problems with the table.
>
>Any idea what is going on ?
>
>Thank you in advance
>
>Gunnar Ennerfelt