On 2017-08-14 10:46, Dave Crozier wrote:
I have a general purpose "Loader" app that loads the .exe from the server onto the local workstation in a pre-defined folder and runs it. This means that updating the .exe on the server is simple as you are sure that it is never open by anyone. In addition I can send the loader instructions to unload the local .exe if there is a workstation server update due. It unloads the local "exe" and sits waiting for a signal to upload the newer updated .exe off the server. And it has saved hors of trouble finding out who has the application open on the network.
Yeah, I put something similar in place years ago. The local EXE basically looks at the server setup/update file and compares its AGETFILEVERSION to the local EXE's version and if newer, does a ShellExecute to run the _update.exe (Inno setup) and the next line quits the current app so no conflict. Been working great; administrator never has to visit any workstations again. And I haven't used DBFs since 2004 (excep for classic FabMate, which my pioneer/original client still loves today).