Now i'm having an issue: I have a container field with a PDF image (vector) on it. if I save this layout as PDF, the container shows highly pixelated.
In previous versions fo FileMaker it worked perfectly, even in 12.
I'm testing on Windows now to see if the problem persists.
What are the issues Donny?
Any error codes? Maybe a wrong file path?
With MBS Plugin you can on Mac script the print dialog and do print to PDF file which may give other results.
For ibrahim, I think FileMaker on Windows uses the preview JPEG of the PDF in the container. We can improve that if you render a high res preview using our MBS Plugins' functions (with DynaPDF). So if the container contains a high res jpeg of the first page, FileMaker could use that one.
The issue is any script that contains the script step "Save records as PDF" it just won't save. I get error number 800 "Unable to create file on disk". And yes, I've checked the path and it's correct. As stated before, this script step works perfectly as long as the OS is NOT 10.9 or 10.9.1.
Has anyone else had issues with a scripted pdf save using version FMP13 or FMPA13 under OS 10.9 or 10.9.1 (Maverick)?
No, it works as expected in FMA13 and Mac OS X 10.9. Also, creating a file in 12, then opening it in 13 and using the script still works for me.
Have you tried deleting the existing step and re-creating it in FM13?
Yes, I am having a similar issue. Unfortunately mine is sporatic. FMPA13, OS 10.9.1. I am saving a multi-page layout with embedded images and text. It will run the save script fine the first time through, but on a second or third time running the script, I receive the error. Thought it might be a permissions issue and have run through the Disk Utility steps to verify/repair the disk. Reinstalled the OS yesterday afternoon and again, first run through, the file was written, next time - error.
Same problem here with FM 13 on OS X 10.8 and 10.9. Worked well in FM 12 also on OS X 10.9.
I claim this has not to do with scripting in itself, but with saving-as-pdf. We have had the same problem. It has been difficult to prove this bug, as it seems to work different on different computers.
There is another known bug for which there is a solution. I believe most people here already did this, which is why they fail to get this save-as-pdf-bug, but that's my theory.
Anyway, after deleting the Adobe PDF plug-ins under Library -> Internet support, this bug DISAPPEARS for all my team members.