Hi Hugo,

what I think is being pointed out is that if you run your app from the network, your error code won't be able to run, wherever you have that in your app. That's a big difference from a local install, where at least you (should) get the information that the network was disconnected.

Hank

>>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.
>
>>
>>using TRY catch would not resolve your problem either because the if the connection is lost, it will stay lost even if the network comes live again. It might not even be able to load the code to be exectuted in the catch, because it has to be read from the executable.... which it cannot.
>>
>>Really the best solution is to use a launcher... it will make your program faster as well.
>>
>>Walter,