>Graig:
>Have you ever noticed that when implementing "RUN/N" for a DOS EXE (and if the DOS EXE does some file work), that the VFP program continues through, even though the DOS EXE file service has not completed? IOW: If the VFP app expects a file immediately after "RUNning /N MyDOS.exe", in some cases, that "DOS" file may not be ready.

RUN/N is supposed to be for Windows programs, not DOS programs. If you expect a file to be created, I would setup a timer and periodically check for the file.

>
>A follow up: How can we determine if CREATEOBJECT() will service executing other apps on the desktop?

Try it and trap for errors.


>
>>>Thanks for the quick response. However, I tried this approach and it did not work either. I got the same results I got when I used the RUN &cexe format. There is a brief DOS window, it quickly closes, and thats it. Any other ideas? Could there be some "set" value that needs to be changed for this to work?
>>
>>
>>No set value. However, I would change the RUN to RUN /N