I have Lion 10.7.3 on a couple of machines and frequently create PDFs from FMPA and then open them without experiencing anything you've reported. Since what you're reporting isn't consistent, then I'd look into the data being used to create the PDF. Is a particular data set causing the problem?
You mentioned that it is inconsistent even on opening. Do you mean that the same PDF will some times crash Preview and some times not, or is it the same file created from the same data set? If that's the case, then I'd look to test your solution on a clean installation of the OS and FMPA. Make sure you've patched the OS, but don't install anything else, especially Adobe. I'd wager that will solve the problem.
Do the file sizes vary on the PDFs? Is there any options (security, etc.) set on the PDFs?
This strikes me as an environmental issue, but I could give it a try on a test box for you if you'd like.
its not the data. Tonigh I created a new file, a couple of fields and the script, as a test. The PDF output also crashes Preview.
Do you mean that the same PDF will some times crash Preview and some times not,
yes. It happens with different databases, and different pdfs, anytime.
A clean OS install is a bit much , but I know where you are coming from. This is 2 differnt systems having the same problem.
I have no adobe.
file sizes are small, eg 29KB for the test output, ooptions disabled
I couldn't tell from your posts whether you are using a scripted Save as PDF process or the OS-level Save as PDF from the print dialog box.
The quality of PDFs and the code behind them is almost always different because they use slightly different postscript engines.
Try using the other method and see if you still get the same pattern of frequent crashes.
If you do, and it's the OS-level PDF from the print dialog box in Lion, then the problem is probably all in the OS.
If you are using a scripted FM Save as PDF script step with the file set to auto-open, then keep track of which app is auto-opening it and see if there is anything in particular about the records for which the PDF crashes.
If one of the PDF-creation methods always opens cleanly and other has problems, that's a good clue as to where the problem lies.
I've noticed this as well lately - Preview will crash when opening a PDF generated from a FileMaker script. Often it will crash the first time I do this, then I click the button in FileMaker Pro Advanced to create the PDF again and it will open successfully, sometimes it will crash again. I don't have Acrobat installed on my machine so I can't compare results but it's certainly been happening more and more in recent times.
FileMaker 8/9/10/11 Certified Developer
- - - - - - - - - - - - - - - - -
Phone: +61 2 9484 6565
Mobile: +61 418 468 103
on 2/29/12 5:27 AMcortical wrote
Simple enough save records as PDF, FMPA 11.0 v4 , no Adobe on my system 10.6.8. The same file can save and sometimes open in Preview and other times cause Preview to crash.
without further info, one aspect i would suspect is fonts – are you using any
user-installed fonts? can you post the crashed thread part of a crash log? that
might reveal something
Scripted save rcords as pdf, not OS Save?send records as PDF
It is not set to auto open
It is always opening on Preview on my system, and Preview by defualt on the client's system.
There is one user installed font on my system, it is not being used, and the Preview PDF issue has been happening for far longer than that font has been insatlled.
A new test file printing one field, Verdana, will crash Preview as databuzz describes.
a logo is a log a logo is a log - typo - sigh.
ah — the emails for this forum do not indicate that there is an attachment, and
you didn't mention it, so i didn't realize you had posted one …
what i see is a Finder crashlog from 20 Feb — is this right? i thought you had
said Preview had crashed; if the PDF export is really crashing Finder that's
on 2/29/12 8:55 PMcortical wrote
attached preview log file , one of 7 from yesterday
okay, it's interesting but not definitive; an assertion failure during PDF
rendering suggests Apple would have a good start on debugging it (assuming it's
more or less the same on 10.7); from the little i can tell from the crash log,
it's surprising that this crash is inconsistent; i'd suggest submitting it to
FMI as a bug with the PDF produced by FileMaker; FMI can't really fix it (as i
understand the PDF code is licensed from Adobe), but FMI theoretically has some
sway with Apple for fixing OS X compatibility with Adobe PDF
thanks Steve. I'll submit the next occurance to FMI.