Tracker Software Products
Online Help System

Home >  >  > Orphaned Pages

Using Drivers API SDK

Who should use the PDF-XChange Drivers API?

Developers requiring the ability to create PDF documents from their own applications (*Clarion Developers - See below) or indeed managing the output of other file formats to PDF from 3rd party applications such as MS Office, AutoCAD, Internet Explorer etc, providing a set of 32/64 bit Virtual print drivers - the PDF-XChange Drivers API is an excellent choice. Creating arguably the smallest and most reliable facsimile in PDF format of the original document available today - at a very competitive price.

Other developer kits available for PDF Creation, Manipulation and Viewing from Tracker Software Products include, PDF-Tools SDK, PDF-XChange PRO SDK and the PDF-XChange Viewer SDK. For more information on all of our developer products please visit our website:

Windows Support

From Version 4 we have dropped Drivers for all Windows versions prior to Windows 2000 - should you still need to support Windows 9x/ME/NT, we have continued to offer our highly successful PDF-XChange Version 3 product range, though it should be noted that NO further development will take place with our Version 3 product line.

Version 5 supports all Windows versions Windows 2000 and later.


The PDF-XChange Drivers API ActiveX

Allows developers to control the properties of the PDF-XChange driver for the creation of PDF documents. Developers are able to harness the full power of our award-winning Driver by specifying parameters for PDF creation as used by many millions of contented End Users - directly from within the developer's own Software applications.

The PDF-XChange Drivers API is supplied as an ActiveX component. Using its methods and properties all operations can be performed.

The sequence for creating a PDF file from a developer's application is:

  1. Create a new unique (and temporary) virtual printer using the IPXCControlEx interface.
  2. Using the IPXCPrinter interface returned by IPXCControlEx, set up all properties as required for PDF creation.
  3. Print to the virtual printer created by step 1, either directly from developer's application or from any 3rd party application run from this application.
  4. Close the created printer and destroy the temporary printer instance created.

*Clarion for Windows Developers generally do not need to use Virtual Print Drivers to output their application reports using our products. Clarion uses a method to output reports to a Windows Metafile format for viewing that our PDF-Tools SDK is able to convert directly to PDF, whilst still retaining the reports formatting and text data - ensuring it is still a fully text searchable PDF file once created - we therefore recommend that unless Clarion developer's are converting 3rd party formats such MS Office, HTML, AutoCAD etc to PDF - they use our PDF-Tools SDK and not the PDF-XChange Drivers API SDK.


In most environments the provided COM facilities are available transparently after the installation and registration are complete. However, for some 32-bit based IDE's (for example, Microsoft Visual Basic 6) running in 64-bit Windows, this may be problematic. In this event, you should manually reference the type library (pxccom.tlb) located in the PDF-XChange installation directory.

See also

Was this information helpful?YesNo