Hi Michael,

Thanks for the feedback. We usually use map drives when our client's IT allows us. What drives me crazy is that the mapped folder is a local drive of the server where our application is installed. When we use the UNC path, the app (or maybe Windows) created network traffic, which was not the case when we used the Folder path.

  This is the application and data location
  SERVER: SRV01
  D:\SOFTWARE\APP.EXE
  D:\SOFTWARE\DATASETS\ZONE1          && 2.5 secs refresh
  \\SRV01\D$\SOFTWARE\DATASETS\ZONE1  && 30+ secs refresh!!!

Using the UNC path was not intentionally done. Our client have three environments (Dev, Test, Prod) consisting of 5 servers, so that we were moving data around to get the best performance. Again, one of the VFP table size: 1.5+ was nearing the VFP limit. Another table has 845 MB file size.

>Hi Ramil,
>
>If you can use drive mapping (i.e. to drive letter:\...) instead of UNC path, that might make a difference. I've noticed that access to mapped drives is often faster (at least initially) for Windows links in general. Just a guess that this may apply to your situation.
>
>Mike