Your definition of external data source may be wrong, not using hosted style path that
I don't think I am using an incorrect filepath, I am indeed using one that looks like your template. And it does work as expected, except it only works for one client file at a time, and not for use from scripts at the same time, either.
So is there a way to overcome that limitation?
when the hosted file is already opened on the local machine (via Open Remote...) then the script fails with an error like this: "[hosted file] is currently in use and could not be opened.
That seems to point to the fact that you are using OS-level sharing to get to the "hosted" file...
That's a very bad thing. Can you give some more info on how you have the whole thing set up?
Well, I go through Open Remote... and I open one hosted file, and I open the other file locally. Then I run a script from the local file that sends a parameter to the hosted file. That's when the error occurs. When I only have the local file openthen the hosted file opens when I run the script. The Window menu at that point will show the targeted file in a hidden winow. When I un-hide that window, then I see the name of the server appended to the names of the file. This seems to tell me that I am indeed talking to the hosted file. Besides, the machines are not set up in a way that I could mount a share from the server on my local Mac.
The peculiar thing is that none of this is a problem when when both files are local, or both files are hosted.
Which makes me think that the problem is the number of connections from my local FileMaker to the hosted file.
I take it this whole thing is something that is not commonly done?
So, it turns out that this problem seems to only exist with FileMaker Server on PC. The Mac version of FMS is actually fine, and things are behaving as expected and the same that you would see when all files are local.
For the record, the server installs were not on the machine used to develop the database files, and both servers were version 14.
So, we have yet something new: All problems seem to go away when we do not specify a folder on the server.
What I was working with, for both Open Remote as wellas External Datasource was something like this:
fmnet:/[IP]/[dir name]/[file name]
The above produced a collision when the client was on a Mac, and the server on a PC.
This problem does not occur when we use this:
You can't specify [dir name]. You can use subfolder (or 2nd database directory), but server shows all files in flat.
Interesting effect you got such an error when specifying it in path Allowing such path can be said as bug...
Agreed with user19752... you can't specify a path. FMS does the hosting and reads from where the files are located. All clients talk directly to FMS (by IP address or DNS name) without any indication of path.
You can see this in action clearly by adding a file reference just by picking a file from the Open Remote dialog. Regardless of where the file is stored on the server (default folder, additional specified folder,...) the file reference syntax will always be
fmnet:/<serverIP or DNS>/<file name>