I would suggest a separate executable, or an administrator option in the .APP file. Don't forget that these are two separate issues -- related, but separate. The first issue is how to update the table structures. I would suggest a routine to do this, as I said above either in a separate .EXE or in an administrator function. This routine would be smart enough to detect the current version of the structure and make the modifications to the new version and it would detect if other users are on the system and not update the structures if they are. The second issue is how to update the app on the users local drive without doing anything. This is done multiple times (once per user), and requires nothing special on the case of the user. In this case, Ed Leafe's & Nick's solution works well. I would suggest an addition that ties into the first issue. Have the startup .EXE detect if the structures require a change from the 'current' version. If the structures have to be updated, and haven't been yet, then don't update the .APP. > 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 > >>> --