PDFF Xchange 4 conflict with older SDK

[ALDEWACS]

Situation:
My PC has PDF Xchange V4 SDK, used to work with our VB modules. It was installed as Build 165, and that's what my clients have installed per my distribution files.
A few weeks ago I also bought the 'User version' of PDF Xchange 4, (Build 167), ostensibly to replace the Adobe Acrobat package I had been using to create PDF's from WORD and EXCEL etc.

I've been having erratic behavior where the newly compiled (after the user version Build 167 was installed) programs are working fine on my development PC, but fail to produce the virtual PDF-X4 printer on client machines (with their build 165). After a bunch of trial and error and head scratching, I uninstalled both of my PDF Xchange packages (SDK and user version) and reinstalled just the SDK Build 165, matching my clients. It all works now. If I install the build 167 "user" version, it fails to create the printer for the client. Hence if we use build 165 everywhere, it seems fine. It is possible that if we use Build 167 (or later?) everywhere, maybe all would be fine as well, but my dilemma is that clients already HAVE build 165 installed, and switching them to 167 will be a serious hassle. Since 165 works I'd sooner go back to the 'User' version Build 165, and I'd guess all will be great.

I'd prefer to just stick with build 165 for the user version, if I could get a copy of that to replace the 167 build.
Is that (ie USER version build 165) possible/available to me somehow?

[John - Tracker Supp]

Hi - Isuspect that this may be the issue ..

Starting from build 167 of the driver, names of options are case-sensitive

To prevent an exception for example in the sample code below this is required - is it possible your issue is similar ?

e.g. This code line :

Printer->Option[L"Email.Enabled"] = L"False";

with this line

Printer->Option[L"EMail.Enabled"] = L"False";

note capital letter M into EMail word.

This was not publcised and I was only made aware of this myself this weekend - so if it is the case - apologies and hope this resolves for you.

[ALDEWACS]

John
Here procedure is where the options are set (there is 1 other line, repeated at the end..)
Seems OK to me, all pretty well copied from original Tracker code I believe.
I wouldn't know where to verify otherwise.
**I guess I suspect this is NOT my issue.**
PS - Is Ver 1.65 of the 'stand alone' PDF Exchange 4 installer still available to replace my 1.67 and match my SDK? Without that I have major problems and much work to do.
Al
=================================

Sub CreateGlobalParams()

'==============================
m_bUseCompression = True 'use compression on the file
m_bRun = False 'no Acrobat start after creation
m_bEmbeddFonts = False 'to be reviewed ADW
'==============================

frmREV_270.pdfPrinter.ResetDefaults
frmREV_270.pdfPrinter.Option("Save.File") = m_fname
frmREV_270.pdfPrinter.Option("Save.SaveType") = "Save"
frmREV_270.pdfPrinter.Option("Save.ShowSaveDialog") = "No"
frmREV_270.pdfPrinter.Option("Save.WhenExists") = "Overwrite"

If (m_bUseCompression = True) Then
With frmREV_270.pdfPrinter
.Option("Compression.Graphics") = "Yes"
.Option("Compression.Text") = "Yes"
.Option("Compression.ASCII") = "No"
.Option("Compression.Color.Enabled") = "Yes"
.Option("Compression.Color.Method") = "Auto"
.Option("Compression.Indexed.Enabled") = "Yes"
.Option("Compression.Indexed.Method") = "Auto"
.Option("Compression.Mono.Enabled") = "Yes"
.Option("Compression.Mono.Method") = "Auto"
End With
Else
frmREV_270.pdfPrinter.Option("Compression.Graphics") = "No"
frmREV_270.pdfPrinter.Option("Compression.Text") = "No"
End If

frmREV_270.pdfPrinter.Option("Fonts.EmbedAll") = IIf(m_bEmbeddFonts = True, 1, 0)
frmREV_270.pdfPrinter.Option("Save.RunApp") = m_bRun
frmREV_270.pdfPrinter.Option("Save.RunCustom") = "No"

End Sub

<< and elsewhere ...>

frmREV_270.pdfPrinter.Option("Bookmarks.Enabled") = True

[Tracker Supp-Stefan]

Hello ALDEWACS,

Asked for some help here as I can't find the error myself.
Expect an answer from our development team shortly.

Regard,
Stefan

[ALDEWACS]

Stefan
I hope we can resolve this 'seamlessly'. Right now I have uninstalled the PDF X4 standalone from my PC and cannot use it as it 'breaks' my apps created with the 165 SDK.
Worse, if 167 (and future 168, etc?) standalone PDF X4 releases break my apps based on SDK 165, there is a serious issue as any clients who might install PDF X4 (standalone) (and which we have been suggesting to them to replace Acrobat Reader), will break our app.

Also if a client installs any other app that uses an updated PDF X4 SDK release, I assume there would be trouble for our apps as well (although I don't know that for sure).
Al

[Ivan - Tracker Software]

This line causes the problem ?

Code: Select all

frmREV_270.pdfPrinter.Option("Bookmarks.Enabled") = True

[Ivan - Tracker Software]

Into new build will revert back params names handling as it was prior to build 167

[ADeeg]

I have a similar problem in the current Build 171.
I get a EVariantBadVarTypError (Delphi environment) by setting Options from the Optimization-Section, e.g.

Code: Select all

PDFPrinter.Option['Optimization.Blending'] := 0;
PDFPrinter.Option['Optimization.UseTransparency'] := False;

Settings of other Sections (e.g. Save, General, Compression, DocInfo, etc.) works fine. I also tried other Up/Lowcase combinations of Section- and Propertyname but nothing works.
The same code on build 161 worked without any problem.

Can you tell me the correct spelling of these both options please?
Thanks a lot.

[Ivan - Tracker Software]

Valid property names should be:

Code: Select all

PDFPrinter.Option['Optimizations.Blending'] := 0;
PDFPrinter.Option['Optimizations.UseTransparency'] := False;

[ADeeg]

Hi Ivan,

great - that work's. Many thanks!
I suggest, you should correct this in your SDK Documentation as well.

[John - Tracker Supp]

Have requested this is done ASAP and will release as soon as ready.

Thanks for your patience.