Great video. Why oh why would Claris deprecate container references ? Using references, I thought, was long considered a 'best practice'. Also, your method gets around the issue, but it involves 3 steps which includes the addition of 2 unstored calcs. Not performant, right ? I suppose we can lessen the damage by making one (or possibly both) of the unstored calcs into a text field with an auto-calc option so performance doesn't take a hit, no ?
Hi C.O.! You are always so faithful to write - thank you! If I am thinking of the same unstored calc fields, I only defined them temporarily to teach how to learn the path to the folder on the shared volume. We eventually deleted those fields as they became unnecessary. As for FileMaker's reasons for deprecating container references, I suspect it was a reaction to the mistakes users were making by inserting files stored in protected spaces. Hopefully, someone with "inside FileMaker" knowledge will chime in here.
@@AccelerateComputerTraining Thanks, Tim. I had paused the video, gone to lunch, and hadn't yet seen the part where you got rid of those extra fields. Nor had I considered that the option to 'store externally' (which is more important) is still available. Thanks for the great feedback!
Hello there. Thank you for sharing your video. I was attempting to use the store data externally, but I would like that data on a different volume on the server. for example, filemaker resides on volume "C". I would like my data from containers on volume "F". I enabled external on server and added the container path as well. when i go to the DB and go to EDIT-->Manage-->Container, the option to add a path is greyed out. I am unable to add one. I do have admin rights and have advanced tools enabled. i searched the net and looked through videos but no one covers how to add the path when it is greyed out. any help would be greatly appreciated.
@@AccelerateComputerTrainingthank you. that makes no sense for them not to allow such a convenience. This would allow for a cleaner data drive and windows drive. plus in case the c: drive gets corrupted, at least the data is save on the data volume. we do not backups of the server, with backup nightly the full c volume to include data files. more work on end-users to do a granular or selected directory path backups to exclude paths not required.
Great video. Why oh why would Claris deprecate container references ? Using references, I thought, was long considered a 'best practice'.
Also, your method gets around the issue, but it involves 3 steps which includes the addition of 2 unstored calcs. Not performant, right ?
I suppose we can lessen the damage by making one (or possibly both) of the unstored calcs into a text field with an auto-calc option so performance doesn't take a hit, no ?
Hi C.O.! You are always so faithful to write - thank you! If I am thinking of the same unstored calc fields, I only defined them temporarily to teach how to learn the path to the folder on the shared volume. We eventually deleted those fields as they became unnecessary. As for FileMaker's reasons for deprecating container references, I suspect it was a reaction to the mistakes users were making by inserting files stored in protected spaces. Hopefully, someone with "inside FileMaker" knowledge will chime in here.
@@AccelerateComputerTraining Thanks, Tim. I had paused the video, gone to lunch, and hadn't yet seen the part where you got rid of those extra fields. Nor had I considered that the option to 'store externally' (which is more important) is still available. Thanks for the great feedback!
Hello there. Thank you for sharing your video. I was attempting to use the store data externally, but I would like that data on a different volume on the server. for example, filemaker resides on volume "C". I would like my data from containers on volume "F". I enabled external on server and added the container path as well. when i go to the DB and go to EDIT-->Manage-->Container, the option to add a path is greyed out. I am unable to add one. I do have admin rights and have advanced tools enabled. i searched the net and looked through videos but no one covers how to add the path when it is greyed out. any help would be greatly appreciated.
To the best of my knowledge, FileMaker Server does not allow us to store container data files on a separate volume.
@@AccelerateComputerTrainingthank you.
that makes no sense for them not to allow such a convenience. This would allow for a cleaner data drive and windows drive. plus in case the c: drive gets corrupted, at least the data is save on the data volume. we do not backups of the server, with backup nightly the full c volume to include data files. more work on end-users to do a granular or selected directory path backups to exclude paths not required.