>>>>>If lnWait is 0 [zero] According to MSDN that means:
>>>>>WAIT_OBJECT_0 0x00000000L The state of the specified object is signaled.
>>>>
>>>>Sorry, but I do not understand what you are saying here.
>>>
>>>That means that the object you waiting for is is available (not sure if that is the right word).
>>>No error here, just you should proceed further.
>>
>>So have they changed the way it returns things or something. Because with the same code on the same machine, but 1 exe built in vfp8 and 1 in vfp9, I run the vfp8 exe and a 238K pdf is built, run the one in vfp9 and a 1K pdf is built and does not open.
>>
>>and if lnWait is 0 and WAIT_TIMEOUT is 0x00000102, then it executes the first part of the if statement, which is exit. It should be doing the 2nd part which is doevent, I believe, until the pdf build is done.
>>
>>Thanks for the help,
>>Beth
>
>Have no idea, sorry.
>But these are all API functions and should the same way no matter what version of VFP you use.
>Could you post what you want to do?
>What happens if you (just for testing) use WSH:
>

>oTest= CREATEOBJECT([Wscript.Shell])
>oTest.Run([command line here],1,1) && Wait until the process is finished
>

I will try that, but this is what we are trying to do. We are using the freeware ps2pdf program to convert ps files into pdfs through vfp for reports. The program can be located here: http://www.1amsoftware.com/vfpps2pdf/index.htm

The only change that we made to the code was to pass in the run string, instead of letting the program build it, before calling the runme procedure.

Thanks for your help.
I am looking into your suggestion and Sergey's also.

Beth