Hi All,

We have an in-house FoxPro application with client end on a mobile wireless
Windows XP Professional PC and back-end on a Windows File Server.
Occasionally the client PC moves to a poor-coverage areas and loses the
network. The application checks for back-end files availability every 2
seconds and initiates transaction only if the database is accessible. The
problems occurs when the network is lost for very short period of time (<2s)
and the polling didn't detect it. The application initiates transaction but
the database file is not available (closed by OS). Then the applications
stops responding with an error 1104 "Error reading file".

I'm seeking advice from IT people with similar problem to:
- detect network outages in more efficient way
- get FoxPro application to know when the OS has closed the file
- trap and recover from FoxPro 9 error 1104

I'm also considering other solution designs like using 'Offline folders', or
DFSR scenario with link target on the XP client but this will increase the
complexity of the solution.

Any help, even raw ideas, is much appreciated