I would suggest not having the launcher run a separate exe independantly. Doing so, will just add more time in your loading process since the VFP run-times will be loaded twice. I would instead build your main.prg into an executable that checks for the update, and runs the main app or exe.

>>>>>I would like to be able to install exe's on local machines on a lan and then have upgrades to the exe's downloaded from the server automatically when I put a new version on the server. I know how to check for a newer version (using fdate()etc.) from my exe, but the exe cannot be running when the filecopy is done.
>>>>>
>>>>>Is there a good way for a windows shortcut to do the checking and copying before running the exe?
>>>>>
>>>>>TIA
>>>>>Terry
>>>>
>>>>I have done this in the past so the details are a little fuzzy. The first option is to use a loader program. The loader program looks at file versions and copies down any newer version. The loader program then fires off the true program and closes itself down.
>>>>
>>>>The second option is to use the network operating system. I think ZEN or NAL for Novell Netware will allow you to write rules that can check for newer versions (based on date) of a program and copy it down. I have not done it under NT Server but my guess would be to look at system policies.
>>>>
>>>>Hope this at least points you in the right direction.
>>>
>>>Can the loader program shut itself down while the exe is running or must it wait for a 'return'?
>>>
>>>Terry
>>
>>
>>In the test I just ran, the loader program stayed resident. I know that I had away of letting the loader program exit while the real program ran. I will search my source code tonight and post the answer when I find it.
>
>Fred, I just played with the vfp external RUN|! command from the loader program. The loader program had a 'quit' after the 'run'. This seems to work ok! The loader program was not resident. Hope there are no gotchas here.
>
>Thanks for the response...Terry