Hello Ed,

After running through the process line by line in debug I was able to determine that the problem was not with code but with call recognition...

The object is created for a DOS command line ( the command line launches another application "Quest" ) and then the DOS command line object closes which allows for the next command line run! The Quest App is still running, 'big problems'.

Can I determine the windows-handle for Quest to force the WAIT to be for it?

>>
>>...You want to make sure that you're using my API_APPRUN class ...download it ..., and then start up an instance of Quest using launchApp - which runs the program and immediately returns control to VFP. You can periodically check the progress of the application using the object's CheckProcessExitCode() method; if returns a value other than 259, the other instance is done.
>>
>>Paste Edgar's code here:
>>DO WHILE .NOT. EOF()
>>. nCNTER= nCNTER+1
>>. cCmdLineOut= Alltrim(REPORTS)
>>. oQuest=CREATEOBJECT('API_APPRUN',cCmdLineOut, "C:\Gupta\", "HIDE")
>>. =LaunchAppAndWait(cCmdLineOut, "C:\Gupta\","HIDE")
>>. Do While .T.
>>.. Wait Window NoWait "Running Quest Report Number "+ str(nCNTER)
>>.. IF oQuest.CheckProcessExitCode() != 259 && 259=ProcessRunning
>>... RELEASE oQuest
>>... EXIT
>>.. ENDIF
>>. EndDo
>>. SKIP
>>ENDDO