As the Yeti is a volume attached to your computer (I assume) perhaps you need the computer name in the path before the volume name. Not sure, but worth a try.
Sometimes the "under the hood" reference to the attached device name gets messed up on a Mac. When you attach an external or network volume to a Mac, the mac creates an entry in "/Volumes" (a hidden directory at the root of the hard drive). When you unmount or disconnect it, the /Volumes reference is deleted. If something goes awry with the connection to that device, the Mac may not tidy up properly. When you next connect the device, it appears in visible references with its normal name, but in /Volumes as something different. Likewise if you have two (for example) two USB thumb drives with the same volume name, they appear ont he desktop with the same name, but in /Volumes they are referenced as samename and samename1.
So my guess in this instance is that the connection to the NAS drive may have dropped out at some point. You can check the situation by opening a Terminal window and entering
followed by return/enter (that's lower-case L, lower-case S). You will probably find that you have yeti1 instead of yeti.
Thanks “robwoof” and “keywords” for your replies. I found the issue, but I still find it strange that FileMaker would not throw an error, yet save the exported contents to the application folder!
Once I removed the “"yeti/necropolis_private” it connected. Has this behavior changed? We used to have to call the volume and the sub volume.
So the entire path that works (if the volume was already mounted) is” "filemac:/ImageExport/" & items_IMAGEREVISION::ArtRecordNumber & ".jpg"
What path shows for the mounted location?
Could it be that the 'Share Point' is not the volume but rather the Folder?
Proper Path information is a function of the OS not FM. FMP asks the OS if the location is valid. If the Path is correct yet FMP cannot write to it then usually its because of permissions. This happens most often with FMS as it uses a distinct user account, not the logged in user.
In most versions FMP will use the FMP Application Folder as the default location rather than fail completely. I've seen this behavior for years.
When I opened “Get Info” for that location is says “//yeti/necropolis_private” –that’s what I assumed that path would be.
Thanks for the info on the application path – I’ve never run into that one before.
In my experience it is the share point that follows the filemac:/
Get info tells you the full volume path but that is not the path you use in a link... But rather the relative path so you could be mounting several different sharepointsnfrom the same volume if you needed.
It may be good practice to reference the volume using an IP address of the NAS. I have also noted that it is good practice on the mac to specify smb:// when mounting the volume via the mac and of course, making sure the volume is mounted on Mac login.
I went through the same problem as mentioned by robwoof, whereby a shared volume was not being accessed by filemaker because the "/Volumes" information was not 'refreshing'.
When I got info on the mounted volume, it would show a dash and 1 after the volume name eg: Volume -1 and this stuffed up all the volume paths in FileMaker on the Mac... because the filepath would not include the "-1". However, in this partuclar case, we had multiple users using the same user name to connect to the shared volume and so I suggested creating 1 user account for each connection and viola, problem has not come back, so perhaps it was not really a 'refresh' problem, more like an identity crisis!
And yes, the Mac does not really error when exporting the file, it defaults to the Application folder. I regularily find myself clearing out files that don't belong from my FileMaker Pro folder..!
That makes sense now – thanks!