Corrupt information on appended / merged PDFs

[kentonmiller]

I am using PDF Converter 3.02 and having issues with PDFs that are created from appending PDFs that were previously merged.
This is developed in VFP 9. I merge an existing PDF file (ex. government doc) with the output from a VFP report (contents), then I append several of them together.
After about the 3rd or 4th page, the text from the VFP report portion starts to get corrupt (ex. "The Quick Brown Fox Jumped Over the Lazy Dog" becomes "T e 2uic. Br8wn F;x"... etc.) This was working fine with the prior version 2.51 and just started with 3.02. If I look at the merged PDFs before appending them, they are all fine. It's only after the append function that the problem occurs. It's not a problem with a specific PDF due to the source PDFs coming from several sources.

Thoughts?!?

[David]

Hello

In order to provide you with more information, we would have to look at the documents that you are merging and the resulting corrupt document.
You can send a description of your problem and the documents to support@amyuni.com and our support team will try and assist you.

Hope that helps?

David

[Any1]

I have almost the same problems.
I also tried reprinting the pdf-files via amyuni and then edit them, also didnt help.

U should have received a sample of the pdf-files im trying to split/merge/append via email already.

[hjohnson]

Was this ever resolved? I'm having the same issue as well with version 2.08 within Foxpro 9

I am generating a large number of individual files (300+) most of them are only single. These are all printed to a tempory PDF file then appended into a memo field. Using an additional instance of the object I then Append the temporary PDF to one already existing file. Not all appended file have corrupt data. It doesn't usually start appearing until about the 10th append and then periodically through out the rest of the document.

The individual (single) files are fine, it's only after the append that some of them become corrupt.

Thanks for you help with this.

Hal



In case you need this, below is essestially what I am doing in VFP 9.0

pdfSingle=createobject('cdintf.cdintf')
pdfSingle.driverinit('Amyuni PDF Converter')
pdfSingle.filenameoptions = 1 + 2
pdfSingle.defaultfilename = sys(5)+curdir()+"Statement.pdf"

PdfDoc = CreateObject("CDIntf.Document")
PdfDoc.Open("Largestatement.pdf")

m.lnPdfpage=1

Select Table1
Scan
report form MyReport.frx to printer NODIALOG noconsole

Select Statements
append blank
append memo statements.Reports from statement.pdf overwrite

PdfDoc.Append("statement.pdf")
PdfDoc.setbookmark(m.lnPdfpage,ALLTRIM(statements.st_name),0)
lnPdfPage= pdfdoc.PageCount+ 1

delete file statement.pdf

endscan

pdfdoc.Save(lcFilename)

release pdfdoc, pdfsingle

[kentonmiller]

I have not heard a peep yet. A bit frustrating to say the least.

[Ger van der Kamp]

We have the same problem concatenating PDFs as well. We're still using 3.02. Has it been fixed in 3.03?

[Ger van der Kamp]

I would like to add some more info to this problem. We have been using version 2.50 for quite some time. We didn't have any problems concatenating documents with this older version. We use the PDF-Converter to convert RTF-Documents generated by our software. We use Word-automation to convert these RTF-Documents to PDFs. We offer our customers the option to bundle multiple documents. For this we set the option to concatenate and use Word-automation to print the documents in one PDF. Converting a single document with 3.02 is ok, but when concatenating multiple document we often get the problem described by the original poster. Our software can produce a lot of debug/trace info so we can find problems. When we enable this, a lot more gets done between converting the documents. With these traces enabled its a lot harder to reproduce the problem. But the problem does still exist. We disable background-printing in word while converting the RTF so by the time we start processing the next document, the previous convert should be ready. Our traces confirm this.

We also notice that sometimes not all the RTF-Documents are concatenated in the PDF. Our trace shows no failure printing the document on the PDF-Converter.

Looking at the example provided by hjohnson, and the fact that enabling our debug/trace output makes it harder to reproduce the problem, I wonder if there is a problem when concatenating files without much going on between the print/convert jobs. Could there be a problem when printing documents on the PDF-Converter without any time between them?

[Jose]

Hello,

The scenario you are describing typically is caused by the fonts not being embedded in the document.

You can resolve this by turning on “multi-language” support when generating the PDF document.

Hope this helps?

[Ger van der Kamp]

We have MultilingualSupport and EmbedFonts set. We also set NoPrompt, UseFileName, LinearizeForWeb, EncryptDocument and BroadcastMessages when creating PDFs.

When we append to an existing PDF we add the Concatenate Option.

Do we miss an Option? Must say that we didn't look at the options when we upgraded from 2.50 to 3.02

[peteb]

Ger, we've been having the same issue. I believe it was narrowed down to v3.02 running on Win2003, but I am not sure on the specifics. v3.03 had been released and that fixed the issue for us.

An additional short-term work around is to open your pdf converter printer properties, advanced tab, and point the driver to v2.5.