>We have a networked app. Our user's all use Win 98 or XP machines. The app and data all reside on a Novell file server. The users all launch the app right from the Novell server.
>
>Every once in a while we'll have a network glitch where everyone, for one reason or another, gets disconnected from the network for a few seconds. The client machines handle the disconnect pretty gracefully and reconnect once they "see" the file server again.
>
>So, if I had Windows Explorer open and our app open when the glitch takes place and don't use either program until the connection is reestablished, Explorer will just continue on as if the connection was never dropped. Our app, on the other hand, will crash immediately the minute I try to do anything in it as though the connection was still dropped. None of the networked resources (programs, data, classlibs, etc) can be found.
>
>Why isn't VFP able to recognize the connection has been restored like other MS apps can?

A networked VFP app must communicate with the server to maintain a list of file and record locks. It also attempts to cache server data locally to improve performance. In addition, the Novell network client may aggressively cache on its own if that caching has not been explicitly disabled.

Reliable network operation is required to properly maintain the locks and cache coherency on each workstation. If the connection is broken, all bets are off. What you're probably seeing is a new connection being established, rather than an old one being re-established - so the new one knows nothing about the former network state.

VFP and other "file-server" databases, because they move a lot of data over the wire, are especially vulnerable to network reliability problems. You can't simply let regular network "glitches" happen with a networked VFP app. Get in a good network admin and get it fixed.