Sergey,

Here is a follow-up question to use of the API_AppRun approach.

Is it possible that one EXE using this API calling approach to call a second EXE which calls a third EXE that uses the API_AppRun method could run into problems due to two EXEs using the same API method during the same time frame?

We are seeing the 1st calling procedure get stopped at the LaunchAppAndWait command during the execution of the second EXE which launches yet another EXE that may well use LaunchAppAndWait. It can get finished sometimes with it's execution of EXE #2, but never gets beyond LaunchAppAndWait.

Any ideas re. how to protect the original EXE from losing it's control?

Note that current test OS is Win98.

Steve

P.s. My first thought is to make sure the process object is named differently in each EXE.