Do you PDFs, when opened in Acrobat, appear to have the content they should?
If so, I suspect that your last used PDF printing setting may have been set to something like print only selected pages or print a specific page# which may not exist.
Go through ALL of your print dialog options screens to be certain the problem isn't in the default print settings Acrobat is using.
Yes, exactly. They appear totally correct - all the content is there.
I might add that it actually does print when you select Print > Advanced > Print as image. However, this is not a good solution in my case because there is a script running which sends hundreds of documents to customers who don't know about this solution and don't understand, etc.
What exactly do you mean when referring to print dialog options screens in the default Acrobat settings?
First of all, this is not a general limitation or issue in the sense that pdf documents created from FileMaker, in my experience, print without difficulty. Moreover there are no settings I'm aware of in FileMaker that would prevent them from doing so (you can specify that a password is required for printing, but that wouldn't produce the behavior you've described).
What that suggests, as per Stephen's comments, is that the problem may reside with the copy of Adobe Reader you're trying to print from. To check whether that's the case, I suggest you try printing one of the pdf files from a different computer (or post one here...). If the files print okay elsewhere, that would suggest that the problem may not be related to FileMaker.
R J Cologon, Ph.D.
FileMaker Certified Developer
Author, FileMaker Pro 10 Bible
NightWing Enterprises, Melbourne, Australia
I see that this one has not been answered.
I have a client who is having the same problem on MaxOS, FileMaker 12 Advanced.
The problem is random.
He can print 8 different reports using different find criteria, each report will be generated exactly the same way by the same script.
From the resulting 8 files opened in Adobe Reader, 7 of them will print, one will not print and will generate the same error messages as bhatt had.
When he sends the files to me and I try to print them using Adobe Reader on Windows 7, I get the same result.
I am finding this impossible to fix because it's so random.
Any ideas anyone?
Rather than using Acobat Reader, test whether the file prints OK from the Preview application.
I too was experiencing these same three error messages when trying to print a PDF in Adobe Reader or Adobe Acrobat that was created using Save as PDF.
Thanks to some clues from the local FileMaker Developer community in Austin, Texas, I was able to arrive at a fix.
The problem was affecting a couple of layouts.
On the first layout, I simply removed the Theme. I changed it back to Classic and everything worked just fine. Save to PDF generated the file and I was able to open and print in Adobe Reader/Acrobat without any issues.
On the second layout, removing the Theme did not work. Turns out the problem was data I had pasted into a field from a Word Document. It appears the copy/paste retained some formatting that was not making Adobe Reader/Acrobat happy. After I stripped the formatting from the data in the field, everything worked just fine.
Joe Gonzalez, CPA
JoeGonzalez wrote, in part:
Turns out the problem was data I had pasted into a field from a Word Document. It appears the copy/paste retained some formatting that was not making Adobe Reader/Acrobat happy. After I stripped the formatting from the data in the field, everything worked just fine.
I've encountered this with embedded data formats being pasted using "text" the users copied from websites.
Because FMPro allows retaining formats on pasted text as the default paste option, I used Custom Menus to replace the actions of the standard Paste shortcuts to Paste Without Style, and our data imcompatibility issues disappeared on newly-pasted text.
I had a user or two who complained about loss of formatting, and explained it to them, eventually restoring the Past WITH Style option, but only as an option/alt-shortcut so they had to invoke it intentionally if they needed the formatting to be retained.
You may want to read "Entering Clean Text (or: avoiding unwanted characters)" at <fmdiff.com/fm/cleantext.html