I have a PDF that I cannot view in a container field. Interactive Content is checked. I assume the PDF file is valid because if I'm in Layout Mode with Sample Data on, the image shows in the container field. But, once I go to Browse mode, it doesn't show. If I view container attributes in the data viewer, it appears everything is as it should be. Any thoughts?
FileMaker Pro 18.104.22.1680
On a Mac
I am having a container field where I store PDF files.
Every time I start the DB and I get to a file in the DB with a PDF in it, I get a box asking me: adobe pdf viewer can not find a compatible… etc.
Now if I select Adobe Acrobat Reader DC it now runs fine, however it will ask me again the next time I open the DB. Boring indeed. Any solution to that?
My first choice would be to use Preview, I did select it when the box appeared but this does not work. Any solutions to that?
If it needs to be Adobe Acrobat Reader DC, where can I set the preferences so it does not ask me all the time?
Adobe Acrobat Reader DC seems also pretty buggy, crashing at time and not allowing to scroll the PDF and a few more bugs.
Any solutions anybody knows of?
By Gary Hoffman
My solution for grad student to upload information about their summer internship, including a PDF file from their employer, is not working well this year.
Last year, we were on FilemakerServer 13 and I built the student-facing layouts for WebDirect. The staff side of the database was accessed through FilemakerPro 13.
The container field does not store its data externally, but rather internally to the db file.
This year, we've upgraded to FMS 14, FMP 14, and, of course, the world has gotten wary of PDF files.
So, our grad students' uploaded PDFs no longer render in the layout where I've placed the container field. If the field is set to optimize for Images, I see a PDF icon and the file name. However, if I change it to optimize for Interactive content (PDF, MP3, etc.), I get an error message that resolves to this: You do not have permission to view this directory or page.
According to FM documentation, interactive content is rendered by the default browser on the platform, i.e. I.E. on Windows and Safari on Mac.
This seems to be new behavior. Does anyone else see this?