The first thing to check is anti-varus program on the server. Try either disable it temporary, if you can, or exclude foxpro files (dbf, cdx, fpt, e.t.c.) from the list of monitored files. See also mskb #Q304482.

>Our network managers have decided that IPX will not be allowed on the network and thus recommended that we move all our VFP data from the Novell Server to the new Windows 2000 server. The data was moved by the network boys and they came to me to create an executable that will access the new server.
>
>So I modified the application to point to the new Win 2000 server and created a load program for the test PC.
>
>I loaded the application on the test machine and ran the exe for a test.
>
>What I found was that the executable runs sometimes 2 to 5 times slower in accessing the data from the new server than the same test using the Novell server on the same machine.
>
>Well I figured that the server may have a speed problem with data, so I did a simple test of copying a 173MB file from the Novell to the PC and from the new Win 2000 server to the PC and found that the file took 1 minute to copy from the Novell server, but 40 seconds from the new Win 2000 server. So the Win 2K server was faster on a straight copy. So that got me to thinking and ultimately asking the question. What could be making the Win 2K server slow in access my VFP tables and databases? Does anyone have any suggestions for me to check on the Win 2K server that would possible speed up table and database access. I am willing to hear any suggestion and pass it to the Network boys.
>TIA