Randy,

The wait state does not need to be complicated. A simple DO WHILE ... ENDDO with a wait state in it like Rodolfo showed is enough. A more elegant solution is to use either API_APPRUN in .VCX form File #9477 or WSH to wait for the VB app to finish.

In respect of the missing file: To test whats going on run the VB app and make the next line after the RUN statement a simple =INKEY(0). This will halt your program untill you press a key. Before doing so go and verify that the file was actually created by using Windows explorer. Is the file there? Can you access it? If so go back to your VFP app and press any key to allow it to continue. Does it find the file? If not what are you using to test for the files existence?

If you can find and access the txt file with Windows explorer then you should be able to do the same via your VFP app. Just out of interest can you post the code from the RUN VB command to the line which checks for the file?


>Jos, thanks for the interest in my problem.
>I am on an XPProf pc that is connected to an NT4 network, but is not really using any of the network resources for this activity. I am creating my file in vb and using an "APPEND FROM thatfile.txt TYPE delim in the statement immediately after. I am using a fairly complex "wait state" program that I got off of MSKB to halt Fox while VB runs.
>
>Thanks, Randy
>
>Possible suggestions from my co-workers
>1. Try another wait-state program
>2. Maybe it has to do with the pc's buffering?