>What are the best options to improving our VFP apps' network connection resiliency? In other words, right now our apps will get a "File not found" error if the network connection is broken. Is there a way to improve this? Especially for wireless connections where it may be lost for a second.

Fundamentally, you can't work around a bad network. Personally, I refuse to support VFP (file-server) applications over wireless networks. I'd try REALLY hard to run a wire to each location that needs one. It might look difficult/expensive to do so, but it's cheaper than re-architecting your app. With your wired infrastructure, servers and workstations make sure hardware and software are configured properly.

If your client insists on spending a lot of money on your app instead of a little fixing their network there are a few things that can reduce, but not eliminate the effect of a poor network:

- switching to a client-server backend and architecture
- work against a local data store, and develop an architecture to synchronize data stores on separate workstations. I believe SQL Server has some built-in replication functionality that can help with this
- code defensively. Open tables only when you absolutely need them, and close them immediately after. Wrap all table operations in TRY...CATCH and all CRUD operations in TRANSACTIONs.