Page 1 of 1

PDF-XChange is not working on a 64bit system

Posted: Fri Mar 17, 2006 9:53 am
by Sage Software

in our application we create pdf-files from Access reports and send them with e-mail. The Active-X component is initialised in the VBA code without using a form.
On a 32 bit system everything runs fine (PDF-XChange Driver Version 3.40 Build 0075)
Now we tried to test our application on a 64 bit system (Windows XP x64) and installed the 64 bit version of PDF XChange (PDF-XChange Driver for Microsoft Windows XP/2003 x64 Edition Version 3.50 Build 0093) instead of the 32 bit version.
Unfortunately there is an error creating the Active-X component, so using PDF-XChange isn't possible.

Here's the code we use:

Dim oPDFObject As Object
Set oPDFObject = CreateObject("Pxc30Com.PXCControl.1")

Call oPDFObject.ClearParams(0)
Call oPDFObject.SetParamStr(0, "Save.Type", "2")
Call oPDFObject.SetParamStr(0, "Save.ShowSaveDialog", "0")
Call oPDFObject.SetParamStr(0, "Save.FullFileName", sPfad & sCaption & ".pdf")
Call oPDFObject.SetParamStr(0, "Save.WhenExists", "Overwrite")
Call oPDFObject.SetParamStr(0, "Save.App.Run", "None")
Call oPDFObject.SetParamStr(0, "Info.Title", sCaption)
Call oPDFObject.SetParamStr(0, "Info.Subject", sCaption)
oPDFObject.Active = False
oPDFObject.AutoApply = True

Can somebody tell me, what we're doing wrong or where the error is?

Thank you for your help.

Posted: Fri Mar 17, 2006 11:25 am
by John - Tracker Supp

Please ensure you have the latest install - this does have some specific improvements for the 64 bit installation.

If you are still having problems :

using pxc30com.dll - please try manually register it using

regsvr32 pxc30com.dll

than test again

If you still have problems - please try the same with the 32 bit version of pxc30com.dll - again manually register it using

regsvr32 pxc30com.dll

HTH - please afvise if you have further problems/ the result.


That didn't help at all...

Posted: Tue Mar 21, 2006 7:13 am
by Sage Software
After this fast answer we downloaded the newest version of the driver (Build 0099) and tried to get our application to work with it, but it didn't help, the same error message occured.
Then we registered the mentioned DLL manually, but that didn't help either.
After that we tried to use the 32bit version of this DLL. We deregistered the 64bit version and registered the 32bit version manually.
After that the line of code "Set oPDFObject = CreateObject("Pxc30Com.PXCControl.1")" showed no error, but the following lines didn't work, the parameters were not set, so the pdf file couldn't be created.

Does anyone have other suggestions how this might work?

Posted: Tue Mar 21, 2006 12:34 pm
by John - Tracker Supp

For now it would seem there is no simple solution to this - other than reccomend you use one of the other means provided for communicating with the driver.

Windows XP 64 requires us to install a 64 bit driver - but your 32 bit app cannot it seems communicate with our 64 bit COM object and our 32 bit COM object will not function with the 64 bit driver.

You therefore have a couple of alternatives only at this time.

1: Convert your app to 64 bit - probably not so easy.

2: Use either the Windows Messaging or ExtEsc methods provided to communicate with PDF-XChange and not the COM object.

I can see no other alternative currently available I am afraid.

Any progress on this issue?

Posted: Wed Dec 12, 2007 11:42 pm
We too would like to use Pxc30Com.PXCControl object (from Office XP).

When we do...

Dim pxcSObject As Object
Set pxcSObject = CreateObject("Pxc30Com.PXCControl.1")

We get Error 429 - ActiveX component can't create object.

Is the ExtEscape method mentioned in another thread an option for developers or does it require the end-user to have a full license of PDF-XChange?

Posted: Thu Dec 13, 2007 1:15 pm
by John - Tracker Supp

Please try to register the 32-bit pxc30com.dll using regsvr32.

With V4 (due shortly) we will provide a separate .tlb file for x32 application use when running under x64.


Posted: Mon Dec 17, 2007 10:33 pm
We copied and registered the dll from a 32-bit machine. No help. Is there more to it (unregister 64-bit?, dependencies?, location?).

Failing V4 to be expected in weeks or months?


Bill Nabors
Online Business Applications

Posted: Tue Dec 18, 2007 2:58 pm
by John - Tracker Supp
I fear there is nothing more you can do for now, V4 is due very soon now - certainly not months.

The end user release should be out the first week after Christmas - the Developer release will be technically ready then too - its the help files and examples etc that will add perhaps an extra 10-14 days to this date.