Hi Gene,
normally your Starter programm just runs the main program, after checking for updates, and then quits itself. The starter cannot update himself, thus another program / task has to do this. The easiest way would be to first install a new main program, which checks the starter for version, and optionally does the update for the starter program. Thus the two can update each other :)
wOOdy
-----Ursprüngliche Nachricht----- Von: ProFox profox-bounces@leafe.com Im Auftrag von Gene Wirchenko Gesendet: Samstag, 5. Oktober 2019 01:03 An: ProFox Email List profox@leafe.com Betreff: VFP App Startup Program
Hello:
I have seen discussions about this at various times, but I have not ever seen details.
You have an app which might be updated and want to have that happen automatically.
In my case, it is a VFP .exe, and I wrote a program to handle that years ago.
What about if the startup program needs to be updated? Since there is a change (the first since) in that, I wanted to write a version that would update the update program, too. Somehow, it did not work. And since there is less debugging information available when debugging a .exe, I ended up giving up on it after some trouble.
My thought was to have two programs:
cbs2run.exe would check cbs2run2.exe if it needed updating (and maybe update), check cbs2.exe (the app) if it needed updating (and maybe update), then run cbs2run2.exe.
cbs2run2.exe would check cbs2run.exe if it needed updating (and maybe update), then run cbs2.exe.
The reason that I had two programs is so that cbs2run.exe would quit running and be overwritable. Even inserting a 5-second pause before trying to overwrite cbs2run.exe in cbs2run2.exe did not work. I got some very inconsistent and confusing results.
Was I overlooking something? If so, what?
Sincerely,
Gene Wirchenko
[excessive quoting removed by server]