Can PDF-Xchange v4.1 for clarion still be purchased?

uncategorized
1

Can PDF-Xchange v4.1 for clarion still be purchased?

PDFXToolsReportClass CLASS(PDFBuilderClass),TYPE,MODULE(‘pdfrpt41.clw’),LINK(‘pdfrpt41.clw’)

If not – alternative solutions to turn CW Report WMFs into PDFs

Thanks

I found this - Discontinued

2

It is no longer available for purchase.
If you already have a license it is easy to move the product from one version of Clarion to another. There aren’t any Clarion compiled DLLs.

I still use PDF-Xchange for projects where it already licensed.

I also use the Microsoft Print to PDF driver by creating a IReportTarget class to support using thee printer drive to print to file.

3

I am setting up client machines to take over my development - they are buying all new licenses of everything - almost $11,000 for a new CW setup w/ 3rd-party

I need to combine many WMFs from different reports into a PDF and this is done at the end of running 1-6 reports. - I cannot change my whole process to take separate PDFs and merge them.

4

Kevin

do you need third party for this? I always used Tracker’s PDF-XChange Tools but I am pretty sure the report to pdf is built in to the standard Clarion now. I have never used it (due to using Tracker) and I have heard compaints it generated bloated file sizes but perhaps that was in an early version and is fixed now?

There is a queue that has the various wmf file names (one file per page) so it should be quite straightforward to merge them into one combined queue before sending to PDF.

hth

Geoff R

5

Kevin,

I have the same issue, we also need to put multiple reports already generated into one single .pdf file. My thinking was to output these reports to a folder and then use a pdf merge tool (command line version - there are a lot of open source options available), using OddJob to call to merge tool and then set the output to the folder I need the single pdf to show.

That is my thinking, have not had time to make it work yet.

6

Kevin,
I have not used it, but @Mike_Duglas has this solution for merging PDFs.

The solution I have used for combining reports:
I combine reports by capturing the queue of WMFs from all the reports into a single queue and then calling a report procedure with this report structure:

Report               REPORT,AT(0,0,8500,11000),PRE(RPT),PAPER(PAPER:LETTER),FONT('Arial',8),THOUS
Detail                 DETAIL,USE(?Detail)
                         IMAGE,AT(0,0,8500,11000),USE(?PortraitImage)
                         IMAGE,AT(0,0,11000,8500),USE(?LandscapeImage),HIDE
                       END
                     END

I loop through the queue of WMFs and print a page for each WMF by assign the WMF file name to ?PortraitImage or ?LandscapeImage (depending on the orientation of the original report).

Mike’s solution might be easier. :slight_smile:

7

I think I’ve done that, but what I know I’ve done is a simpler way to combine 2+ (N) Reports. #1 save the WMF files for reports 1 to (N-1) by either renaming or copying the files before Close(Report). #2 in the Nth Report at the end add those saved WMF files files to the Preview Queue and they will print. #3 you will have to delete those saved WMFs.

CPCS has this feature as an extension template that makes it easy to do.

8

That does work but it doesn’t allow you to mix portrait and landscape reports.
The solution I’m using does let you mix them.

9

I quoted the Core API page below that says you must email and ask. I’ve had clients approved in the past few years saying “We’ve had your PDF stuff all working for years and need no support. We just want to pay you for unlock codes to 3, 4 and 4.1 to keep using it.”

  • The PDF-XChange CORE API SDK provides developers with libraries and API for the creation and manipulation of PDF files.
  • Please note that PDF-XChange has now stopped almost all sales of software developer kits.
  • Available to approved developers on application - please contact sales@pdf-xchange.com for further information.
10

Yes, thank you. I have reached out.

11

John originally posted this in 2016:

We worked with him for a while about possibly taking over the Clarion side of the product, but ultimately decided against it because PDF-XChange had been completely rewritten under the hood and it would have been like starting over at ground zero to bring it into Clarion.

After some period of years we actually got a notice from John that they had decided to withdraw the product from Clarion entirely. I suspect this was because it was becoming a support sink for them.without Craig to take care of things.