Can't be done on purpose. NAS is always a no-no for hosted files (and their RC data). That connection is general much more fragile than internal disk i/o and a lot slower too. And it implies OS-level sharing to be able to mount them in the first place, which is a second big no-no.
Even if someone found a hack to make it work I would still very strongly recommend doing it.
You can still track those files by using a reference to them instead of making them embedded.
Thanks, wimdecorte. I supposed to you meant "recommend NOT doing it".
The issue with using referenced container is that WebDirect clients cannot export the file from the container. I saw that issue documented, and could confirm that exporting the file didn't work.
correct: NOT recommend it
Did you use the path for "additional database folder"?
Which user did you use for SSH? fmserver?
Yes, I used the path for additional database folder.
But, no, I did not use "fmserver" to login to SSH. I used my own login name.
Then in FM Server I used my user account (instead of fmserver) , and also added my username to the so-called daemon group:
sudo dseditgroup -o edit -a myname -t user daemon
I tried following instructions from this thread:
What would be the "correct" way?
All right ...btw do you know if 360works SuperContainer would help in my case? ie have SuperContainer upload files to the NAS via WebDirect client, and have WebDirect client download files from the NAS to their own computer. I'll have to test out the demo product to find out.
I wanted to add that the username and password I used for SSH are the same as the username and password in FM Admin Console. On the Mac, I have the same username but a different password. Would that cause any issues?
All right ...btw do you know if 360works SuperContainer would help in my case?
Yes, it would help and work with the NAS.