At 13:11 2019-10-07, "Tracy Pearson" tracy@powerchurch.com wrote:
Gene,
How you launched the 2nd executable from the 1st executable may have been a cause. The VFP RUN command will block if you don't use the /N clause with it.
I did use run /n. It works like a charm with my one-level loader.
The ShellExec API should have returned control allowing you to exit the 1st executable. There are a couple of API's that will wait for the 2nd executable to return before continuing.
The VFP RUN command the CMD window to run the 2nd executable. ShellExec will not.
So how does this make a difference?
It is bothersome trying to debug this, because I can not see what is happening. Because the loaders are .exe programs, I do not have the benefit of the debugger, etc.
I have been wondering if having two VFP .exes running at once is an issue. (Is there a conflict between config files?)
[snipped previous]
Sincerely,
Gene Wirchenko