>>>I have a client using SBT Pro Series 5.0 over a T1 line. They are experiencing random "cannot read file" errors at their remote location. They suspect that there may be a setting (either in VFP or NT) that would increase the amount of time that it searches for a file before timing out. I was wondering if anyone is aware of anything like this. The TIMEOUT in the CONFIG.FPW is set to it's maximum, but has had no positive affect on the problem.
>>>
>>>Any ideas would be appreciated,
>>>
>>>Rod Lewis
>>
>>I believe that this is much more a hardware/network configuration issue than a VFP issue. How is your link made... PPTP, lmhost? Are you just mapping a virtual drive and running the app from there?
>
>Erik,
>Their mapping a virtual drive for the data. The application is running on a local server and accessing the data over the T1. Right now the tables are all relatively small since they are in testing mode rather than full implementation. The problem is totally sporadic but seems to manifest itself much more if they are in the application and remain idle for an extended time.

Have you tested when this happens if the connection to the remote drive is still alive? If it is, does it tkae a long time to open a file from Windows explorer? I think that your attentions should be more turned to the network side of this... that is- why is it timing out in the first place? I wish I could be of more help here, but networks are not my forté (which would seem to imply that I have a forté in the first place :-))

I am fairly confident that you can't adjust a file read timeout within VFP. Connection and query timeouts, yes.