>>>>>>MS intent is to have the main exe launched directly. Updates would be a separate thing. Anyone have alternative suggestions?
>>>>>
>>>>>Mike, I don't know if this can be of help, but in our setup the launcher is the sole executable. The equivalent to your "legacy app" is really a Fox app, so the process that is running in the system is the launcher.
>>>>
>>>>How do you update the executable of either the launcher of the legacy app? I did think to send out an email with a link.
>>>
>>>That's basically what we do, Mike. In our case, the local sysop is notified of the availability of updates, download the files, put them in a deployment folder in their LAN, and the launcher will perform the update of the app.
>>
>>We do the same. Does the user start the launcher which then starts the app OR is the new app put onto the user's PC which the user actually starts?
>
>The user starts the launcher. The application is a real Fox "app", as I mentioned above. It isn't executable by itself.

When we get a crash, this is what the call stack looks like:

C:\appfolder\launcher.EXE
C:\USERS\someuser\appfolder\legacy.EXE
blah.FXP
PROCEDURE form.textbox.VALID C:\USERS\someuser\appfolder\forms\someform.SCT
ERRORHANDLER.FXP
LOGERROR.FXP

The launcher is more of a step ladder. I guess. :)