PDFCreator v2.2.1 VBA Support

PDFCreator PDFCreator English
1

Hello. I am have inherited a suite of VBA based libraries that use the older COM Model using the PDFCreator.clsPDFCreator reference based on version 1.7.1 and below. 


When I installed v2.2.1 I have ended up with the problem that the reference to PDFCreator.clsPDFCreator is nolonger available and that the new interface requires you to use anew ProgId such as PDFCreatorBeta

This causes me grief as now all of the production code will fail unless I change it to use the new ProgID and everything that may entail.

Plus what happens when it comes out of BETA I assume all of the reference will need to change again as the ProdId was PDFCreator and will possibly change to something else.

Also, it appears when I installed v2.2.1 it went in as a 64bit object but we run 32bit versions of Office due to other 3rd party add-ins being 32bit only.

Please provide some guidance and options for a newbie to PdfCreator to move a legacy app using a legacy version of PDFCreator to the new version whilst still staying on Office 32bit.

Thanks
2

Hi,


since the not only the names have changed but the COM interface was completely rewritten after version 1.7.3, you will most likely need this manual: http://docs.pdfforge.org/pdfcreator/latest/en/pdfcreator/com-interface/
and to rewrite the entire code, or stick to PDFCreator 1.7.3 for this use case.
We are aware the change causes a lot of work for many users, but the old COM interface got to a point where it couldn’t be maintained properly anymore. The new interface was designed to stay backwards compatible to the current version for all future updates, it has now also left the beta status.

best regards,