@StefanM64 wrote:
Hi,
found many references to this, but none that really provided a correct answer.
I’m using PDFCreator 2.5.2 (due to customer restrictions I can’t use a newer version).
PDFCreator is installed on German Windows 7 64Bit, I’m trying to run the sample VBA macro testPage2PDF in file Testpage2PDF.docm located in install directory under "…\COM Scripts\Word - VBA. I’m using Word 2010 32Bit.I get the error 429 on the line with CreateObject( ):
Sub testPage2PDF() Dim fullPath Dim PDFCreatorQueue As Queue Dim pJob As printJob Set PDFCreatorQueue = CreateObject("PDFCreator.JobQueue")
PDFCreator seems to be coprrectly installed. I can create a PDF test page using dialog in PDFCreator.exe. I also enabled tracing using the Debug options by PDFCreator. But log file is empty as the object cannot even be created, so there is nothing to trace.
What I don’t quite understand ist when checking the registry (using cmd.exe running as Administrator):
if I use regedt32.exe from C:\Windows\system32 (note that this is the 64Bit registry) I find
ProgID “PDFCreator.JobQueue” under HKEY_CLASSES_ROOT\CLSID{66A9CAB1-404A-4918-8DE2-29C26B9B271E}But when I use regedt32 from C:\Windows\SysWoW64 (note that this is the 32Bit registry) I don’t find any ProgID’s registed for PDFCreator.
Maybe this is my problem as PDFCreator seems to be a 64Bit application a thus is registered in 64Bit registry. But Word 2010 is 32bit and cannot resolve ProgID given in CreateObject.
I can’t imagine that the creator’s of PDFCreator are not aware of this problem and that I’m still doing something wrong…
Any help is higly apreciated.
Stefan
Posts: 1
Participants: 1