Any guidance on this please? I am sure that the two issues are related. Our app uses WinExec to start another app. Later on it uses IsWindow on the window handle to see if it is still there. WinExec pauses for some 20 seconds after starting the other app. (Things go totally screwy if you then kill that app before the WinExec has finished). I am having difficulty figuring out which "WaitForInputIdle" is being executed. The magic is fine on the window block as it comes out of CreateWindowEx but is damaged by the time the WinExec returns. Bill
On 08 May 2001 22:55:49 GMT, "Bill Medland" <medbi01@accpac.com> wrote:>Any guidance on this please? I am sure that the two issues are related. > >Our app uses WinExec to start another app. Later on it uses IsWindow on >the window handle to see if it is still there.<snip> This will not work for now (the windows handle are not common across processes) Gerard