Hi Jim,

Thanks for the feedback. No offense but I noticed that the KB applies to VFP versions 3,5 & 6. Probably, MS forgot to update the KB to include versions 7 & 8. <g>

The IT guys of our client traced network traffic coming from our application originating from the Citrix server (SRV01) to another server (domain or DHCP) then back to the Citrix server (SRV01) when the DataLoc property was set to a UNC path. After changing the property to use the "Dataset\Zone1" folder which is located directly underneath the EXE in local drive D:, the network traffic from our app was gone.

Might this be more of a Windows network issue as opposed to VFP? I know that production servers (ie. SRV01) are located in North Carolina and the domain server is located in New York.

>Ramil,
>
>The following is from MSKB #Q136920:
>There is no delay internal to Visual FoxPro caused by the use of UNC to reference files. There is no proven speed or reliability increase given by connecting a network drive to the server and using conventional reference methods.
>
>This sounds like there could still be other factors to consider for the whole, but at least it's something.
>
>good luck
>
>>Hi all,
>>
>>I was hoping someone can confirm if this is normal behavior for a view. Our application (VFP7 SP1) is running on a Citrix server running on Win2K which is part of a Windows domain. One of the VFP table is about 1.5 GB. The database is located on the same server. The application is slow by VFP standards; 2.5 secs average to refresh a grid. Then suddenly, the response time spike to 30+ secs! No code change whatsoever, even a second dataset, same application, which had a 1.7 GB table had better response time!
>>
>>After much hassle and investigation, we found out that the DataLoc, one of the framework property that holds the directory/folder where the database is stored was using a UNC path. This is the comparison of the two settings:
>>
>>

>>
>>Setting 1                      Setting 2
>> Server : SRV01                 Server : SRV01
>> DataLoc: Dataset\Zone1         DataLoc: \\SRV01\D$\Dataset\Zone1
>>
>> Avg refresh: 2.5 secs.         Avg refresh: 30+ secs.
>>
>>

>>
>>After the DataLoc was reverted back to Setting1, everything went back to normal. I would very much like your feedbacks and/or comments about this behavior.
>>
>>Thanks.