Hi!

In addition to Christian Isberner's Idea, i Would suggest another Possibility:
Build a Loader.exe Programm for your VFP Program.
The Loader is located in the Network.
The Users start the Loader.exe
The Loader.EXE copies the VFP DLL's and Your EXE (and what else needed) to the Local user APPData Directory, and then starts your VFP Exe locally.
By Config the locally EXE only loads Data from Network, no internal Resources.

We've Done this (with a little bit of Work ;)) because we've had the Same Issues like you, since years, not always bud sometimes.
This work was worth ist. The VFP EXE ist much more Stable AND is much faster than loading it from the network (depending on Network speed).
And (we use SQL Server) we can reconnect, if the Connection fails.