>Hello all,
>
>I would like my users to run their VFP app from their local (C:) drive. I would like to place the Exe on a common network drive and have a 'Launcher' program always compare the network and local copies of the exe and update the local one if needed. This way, the network exe is never in use and can be updated without having to ask users to exit the app.
>
>Can I, say, have a small Launcher app that checks, updates if necessary and then executes the main (local) exe when it ends ? I don't want the launcher to stay in the stack. I'd like it to terminate.
>
>THe users' shortcut always points to the Launcher. In most cases, the delay is unnoticeable as the main exe is launched almost immediately.
>
>Does this make sense ?
>
>To push this further, this solution would also be used if the main exe is placed on a Sql Server. Clients can then get updates if needed.
>
>Thanks in advance...
>
>Henry

Henry,

Check out my Simple Application Launcher in Files Section/VFP In General it does just that...

Nick