Hi Sergey,

Yes, very true, it is a workaround. As stated, the problem presents itself when the call to SHELLEXECUTE is issued and PRINT2PDF goes into it's loop waiting for the second PDF file to be created.

I am at a loss as to why GSWIN32C.EXE is slower or not functioning correctly the second time around, causing PRINT2PDF to continue without the PDF being created.

I have other programs that use PRINT2PDF to create multiple reports that perform just fine. But I cannot see anything in this particular application that would cause the problem.

Do you have any ideas about the SHELLEXECUTE call hanging up?

Vince