This error message is usually the result of an error in the file path. You may want to post your script.
And has been previously noted in a number of different posts, error message due to a failure to create a new file cannot be overridden by set error capture. Better handling of error messages was one of my "WishList" items posted here: http://forums.filemaker.com/posts/56b3613440
And another common cause is when the path is scripted, the file name no unique and the file already open, for instance if you run the script one more time.
Been investigating this as much as possible from my side and testing on as many combinations as poss.
No, its not the path.
No, its not already open.
This ONLY happens in FMP13 on Mac not Windows, the SAME file opened in FMP 12 works perfectly well. It appears to therefore be an issue with 13.
I still suspect that it's the file path--especially given the fact that it happens only on the Mac as a file path can be valid on one platform and invalid on the other due to the fact that that file paths start with a volume name on Macs and drive letters on the other. File paths have to be letter perfect and the "tags" you start them with are case sensitive. So I suggest that you share the code/calculations used to compute your file path.
You may also want to use the file you can download from this thread: Exploring the use of a $Path Variable in Scripts
I often use this file to debug file paths by inserting a file from the location in question "by reference" and then checking the calculation fields inside the tab control to compare the "file path that works" to my "file path that fails" to discover what detail is incorrect.
Unfortunately not related to created paths
If I go to the SaveRecordsAs PDF via the menu i enables me to create a name and select a folder but then will not let me create the file as it says he disk is locked.
Repeat - this is only a problem with FMP 13 locally and once it locks itself there appears to be no workround
That sounds like the access permissions to your local machines directories may need repair.
why does it work always with FMP12 in the same directory??
what does it work with other software like InDesign in the same directory??
would point to in not actually being the permissions.
Reboot Mac. Run script in FMP 13. It works. Run script again3 or 4 times. It works. Run script again. It no longer works until a complete reboot.
Seems like FMP is seeing a lock - which isn't actually there - and deciding it will no longer work on that, or any folder. That completely feels like a FMP bug to me.
I'd still try that fix and see if it helps if only to fully rule out the possibility.
Please note that there are many other folks "out there" with your OS version and version of FileMaker that are not reporting this problem. That strongly suggests some kind of issue with your machine or the software installed on it.
I claim this has NOT to do with the file path. 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. :D
Just upgraded to Pro Advanced 13!
Have same issue exporting to .xlsx!!!!
I tried adjusting the path variable.
original: "file:" & Get (DesktopPath) & "ALL VENDOR EXPENSES" & ".xlsx"
tried: Get (DesktopPath) & "ALL VENDOR EXPENSES" & ".xlsx"
OUTPUT FILE PATH
Also tried removing the filemac and filewin and just have $path only
Ok..I rebooted the HOST computer and the CLIENT computer. It exports without the error above..except now I get this:
I went to follow instructions on how to deal with it...and they said I should change my HD name..do some other stuff.
Thank you for your post.
Are you able to export to an Excel file manually?
How much room do you have on the local disk?
If you quit and relaunch FileMaker Pro (to clear out the Temp folder), does the issue still occur?
If you create a new file and export Excel, does this work?
Any other information you can provide may be helpful in narrowing down the possible causes.