I have found that if you place a msgbox("PDF Created") instead of the DoEvents inside the second do/loop where it's waiting for the PDF jobs to complete. It will stop the whole thing hanging.

I am running a single PDF print of an Access report and this works for me.

I know this is not a technically superior fix but it does break out of the loop without breaking the PDFCreator software.

The downside is the message saying "PDF Created" popping up but at least my fix doesn't have any other side effects and you know for sure that the PDF jobs are completed. Perhaps my way of dealing with this problem may help someone else who knows a lot more about the software involved find a solution.

Maybe there is a way someone can write something similar to the msgbox that doesn't pop-up on screen but that creates a similar system interrupt.

Trevor H

I have similar problems in my Visual Foxpro applications. PDF Creator breaks, creating corrupt pdf files and corrupting the system's graphical resources (buttons and window painting go wakoo, buttons and menus have no captions or captions with little black and white boxes). This happens system wide and is not limited to my software only.

What is the problem? This didn't happened before and nothing's changed on my system but the upgrade of pdfcreator.

My setup: Windows XP SP3 up-to-date, Visual FoxPro 9 SP2

I forgot to mention that i'm using PDFCreator as a standard printer, not automation or somthing elese.