Recognizing when it terminates. I don't exactly remember the sequence but roughly what happens is:

-Launch word instance 1 using this code (or similar)
-From another session launch another word

One of them was immediately returning as if word is terminated (I dont' remember exactly as I said - it might be instead 2nd watcher is returning when 1st instance terminated, only one of them is waiting IOW and it was the case if I used WaitFor* winAPI too).
Cetin



>I guess I could play around with it and see if it can be done. Which part failed? Does the app fail to launch or does the code fail to recognize when the process is terminated?
>
>
>>I didn't ask for him, asked for myself:) I thought I might have given up early.
>>Cetin
>>
>>>Honestly, no. I've only ever used it to launch non-automation supported apps from within VFP when I want to pause processing until the external app is closed. I wouldn't go this route for automation supported apps. Is he wanting to do that? I must have missed that part of the message...
>>>
>>>
>>>>Tracy,
>>>>Have you ever tried this with office applications like word? Last time I tried to build something around this it was failing (one of the instances were returning immediately - word behaves like an MDI while Excel like an SDI) if I call it for a 2nd instance of word and I gave up.
>>>>Cetin