PDF previews are handled by the system. Every rendering issue I've ever had with PDFs has been solved with either the install/uninstall of acrobat pro and reader. I haven't run into the issue on mac yet, but could you try updating to 13.0v5 that was released this week to see if that corrects things?
Also, what version of OSX are you on, and do you have acrobat or acrobat reader installed?
It does unfortunately happen on the Mac too...
Which is a shame given that preview is not a standards compliant PDF renderer and the Adobe tools outside of FileMaker are the other thing that I make money with, so am in no rush to remove them
It's a 13 issue though.
I have updated on
- 13 ov5 today and the problem still exists.
- The Mac OS version is 10.10.2
- And I use Adobe Acrobat Pro 11.0.10
I think everything is up to date, but the PDFs crash Filemaker Pro
Advanced if I tip "interactive"on. I fear much for my data when crashing
is happening. The database only crashes when I am on a layout with a
container, PDFs in it, interactive mode.
Any hope that this will change? Otherwise the PDF viewer is totally
Am 30.01.15 um 15:50 schrieb Mike Beargie:
The handling of PDFs in containers always crashes my FM Pro 13.
Antwort von Mike Beargie
in /Discussions/ - Komplette Diskussion anzeigen
Some people have had success by removing the Adobe plugin in the safari prefs folder..
If I can remember where the three is I will post it for you...
Did you find some information on that? And is there any Information From Filemaker on that problem?
This has been an issue for me in the past - and upgrading to 10.10.2 brought the issue back. (Note: I'd been holding onto Mavericks until the 10.10.2 update, so I dealt with this issue in the past couple days).
I prefer using Apple's Preview application over Adobe products, especially with FMP interactive containers. In order to get FMP to use Preview instead of an Adobe product, the first thing I did was delete these from my library: AdobePDFViewer.plugin and AdobePDFViewerNPAPI.plugin
This had worked in the past & worked in 10.10.2.
However, I experienced horrendous problems with loading & scrolling PDFs anyway - both inside FMP and just in general with Yosemite, and regardless of whether using Preview or various other PDF viewers. Has that happened to you too?
A quick googling will reveal this is not an uncommon problem with Yosemite.
In any event, I found a solution that worked for me & maybe it will work for you. I found that some PDFs worked just fine, but some didn't. The one consistent difference I found between the ones that worked and didn't work was in the metadata re: PDF Producer. The PDFs seemed to work fine if they were produced by Mac OS X 10.9.5 Quartz PDFContext...or something like that. So to get all my PDFs like that, I did this:
- launch Automator
- drop in the subject PDF(s) (which will put them in a "Get Selected Finder Items" action box)
- then use the PDFs Action "Set PDF Metadata" (which rewrites the entire PDF document in place)
Do not try this with the PDF(s) from external folder itself. It is ABSOLUTELY IMPERATIVE to first export the subject PDF(s) into a separate folder, then "Set PDF Metadata", and then import the PDF(s) back into the source database.
did you assign more memory / increase the cache memory settings in FMP?
Well the increase to 512 MB did not make FM like the PDFs It is still braking down after some ten seconds using a PDF in the container... Very frustrating, also as the "consistebcy check" while reopening my database gives me the feeling that I will crah one day my database at all..
This is a known bug:
I succeeded with a hint by another fellow:
What seems to work, to my experiences:
- use only 1 Container Field per Layout
- optimise field for: • Pictures (don't use • Interactive/PDF!)
It's always the Adobe Plugin. Remote them from the Preferences Folder.
I'm not affected by this issue but for clarifications. Remove all Adobe Prefs, or:
Its a solution.
But surely not the problem, so in fact merely a distracting technique
The problem is the interaction of FMP with Adobe software, and the fact that I can't be expected to get access to manage all users machines to provide a temporary workaround for something that need sorting at the root level.
Please continually report this as a bug with FileMaker until it is fixed, and it is demonstrated that it it fixed.
How EXACTLY does this help me when a core business process is the very link between FMP and InDesign to create rich documents from FileMaker data being output as PDF or print??
This will remove the apparent appearance of your issue, not fix the problem.