I can appreciate your potential nightmare.

I worked at a shop in Las Vegas where the network was less than optimal and the project manager actually asked us to code the system to accomodate a potential disconnect several times a day. I suggested that it seemed far more practical to just, perhaps, make the network a bit more stable, and I was branded as having a bad attitude.

Ha!

I think perhaps Foxpro may rely on an IP connection handle ... if the connection breaks, even though you have a value in a variable containing the connection handle, THAT PARTICULAR HANDLE is no longer valid. If the connection were to be reestablished, then the handle might possibly be a different number.

Going back to my thinking back then, if the program were to operate on cursors or temp tables and reconnect to (USE) the main tables only when a data change was pending, then perhaps this might be possible. But it could be a fundamental design change.

...Art


>This main form is a list of accounts. When you select an account the
>database is requeried to get the details for that account. The details
>are displayed. Simple normal stuff.
>
>I am running the app from a workstation. The exe runs locally. The data
>is on the server and I have a drive letter mapped to the app's home on
>the server. Still simple normal stuff.
>
>I reach down and disconnect the network cable from my workstation.
>I wait 30 seconds and reconnect the network cable.
>
>I still have not touched the keyboard or mouse.
>
>I select an account to see it's details.
>
>The app crashes because the requery fails.
>
>Is this normal VFP functionality? Is there any way to correct this?
>
>Thanks,