>>It is IMO bad practise to run from the network. If the workstation goes to sleep/hibernate, wake up, it will have lost the networkconnection and you'll have exactly this problem. It might not have to do with any DBF, but running a function or form or even displaying an image could cause this.
>>
>>VFP exes are not 'real' executables. When the exe runs, it will read data from the exe file during execution. Normal PE executables will first load entirely in memory before they are executed.
>
>It really does not matter, when the network connection is lost you are in trouble whether you are running the EXE from the local drive or a share, as the data is most likely shared and you will either get an error reading file or an invalid seek offset anyways, and it is an irreversible problem, as you said in the next paragraph, it might be better to run from a launcher, but not for this reason in my opinion.

We're talking about dbfs embedded in the exe, which are read-only. Sharing being irrelevant in that case, as there are no writes, no locks. From local drive, i.e. user's own %temp% folder, practically exclusive.