Jim, Arnon is right (as usual :)
In the next version I will include also processing of the batch file which is supposed to take care of changes, other than just updated app file. It may run another .exe to do something.

>Thanks Arnon - I thought it was "too good to be true" for *ALL* cases.
>A great technique for basic bug fixes and minor enhancements though!
>
>regards,
>Jim N
>
>>Jim, because tabel structure changes is something that has to be done when
>>all users are off-line by an "administrator" (or by a sibgle person anyway)
>>you just send out a special .exe which is run by that person once with out
>>relation to the regular update scheme (this is what I do anyway )
>>
>>Arnon
>>> Nick,
>>>
>>> Cool! But *how* do you handle the case where, say, a table structure has
>>> changed?
>>>
>>> Inquiring minds need to know
>>>
>>> Jim N
>>> >
>>> >It was in January 97 FoxPro Advisor, the article by Edward Leafe called
>>> "Launch Updates of your Application Automatically".
>>> >I just finished my version of this Launcher program, based on ideas of
>>> this article, and it works pretty good. Launcher.exe has size of just 50
>>> Kb, and runs MyApp.APP. I added to it also functionality, which
>>> automatically shows updated README file, to warn users of the new version
>>
>>> features. There is ASCII text .CFG file used to save preferences.
>>> >
>>> >Nick
>>>