This suggestion is very similar to what we did at my last job. We had a timer that ran and periodically checked for a file "kickme.out" and if it existed, gave the user's sufficient time to exit the app with a warning. If the user's didn't exit, it exited after a period of time. This worked for us, but I like the launcher solution better. We did table updates at night.
Tracy


>>>>What if application change also involves adding/changing some tables (and their structure)?
>>>>
>>>
>>>What we used to do (where I previously worked) was, at the beginning of the code, have it check for something in the database that would be new since the last update. If it is not there, then run some extra code (like in a db_fix.prg), that would go in and update the database to the new level you need.
>>>
>>>Next time it runs, it would ignore this, and skip it.
>>>
>>>But you have to keep db_fix updated with any new changes to the database (must be in sync or all $#!!#!#$#$ breaks loose!!
>>>
>>
>>Mmmmmmmmmm on more reflection, I remember we had to get them out for the update to work.... so this would not work with the automatic downloading of the new exe.
>>
>>sorry...
>>
>
>Ahhhhhhh but if the newly downloaded exe would update a field in a base table, and all the apps have a timer in them that would periodically check this base table field, and find it, let's say "True", then throw up a warning form that they need to exit to allow updating of the tables....
>
>Then when the newly udpdated exe finally takes control (exclusive use of some key table), then do the database updates, then set the field to "False". The other older apps now see on the form a message warning them to also exit and re-enter the program (a new one downloads).
>
>Might work!
>
>Tommy