Well I believe it could happen if the application's NIC has power-saving turned on.

Long ago I also saw similar reports, and other strnge things, if the server is handling a large print job, as a priner server, at the same time.

good luck


>I am trying to resolve a problem which is happening occasionnaly. We have an application which is running on a secondary server which uses tables from the main server. Occasionnaly, the application reports an error saying that the a specific table is no longer available. This is cause of the drive f: no longer recognized. Drive f: is the mapping to a drive on the main server. So, we changed that to UNC mapping and this did not help. So, we changed the use of the table for a SQL passthrough. This did not help as well.
>
>When this is happening, all I have to do is to force a kill of the application and simply click on it again to start it. So, the connectivity to the drive is still valid but the application no longer recognize it. How can VFP simply loose the connectivity to the drive and will simply see it again when I restart the application?