1 of 1 people found this helpful
The problem is that there is only one option for where the container data gets stored with a self-contained copy, so it's easy to automate that option.
However, with the various options for different paths and secure vs open storage with external container storage, there is no single option to create and manage all of those possible outcomes. Those options need to be managed by a knowlegeable user at the file level rather than by some defaults.
Thank you Stephen.
Presuming all containers were to be 'unpacked' back to relative paths, is there anything I can do to make this a less cumbersome task for my users? Right now, based on my understanding, every time they do this they will have to go to *every* container field (thankfully I've kept containers in seperate tables so there aren't that many) and set it to store externally along a relative path and then do the transfer (or delay it till the end). Is there anything I'm missing that could simplify this in anyway?
Thanks so much.
Correct me if I'm wrong, but you seem to be addressing the ability to script 'packing up' the database. I'm looking to script the opposite:
"unable to find an equivalently simple/scriptable approach to 'unpacking' the self-contained copy"
Presuming all containers are being unpacked back into relative paths and the name of the database has not changed, my hope was to save my users the trouble of invidually resetting every container field in the database manager.
My booboo, sorry. I read your original post again and I see it actually says "CAN be scripted"; for some reason I read the opposite.
See notes here.
It seems the option is made for FMGo user.
If you provide the file to FMPro user, it is easier that copy all folders with fm flie.
1 of 1 people found this helpful
According to me this can't be scripted because you have to change this in the 'Manage Database...' dialog.
Nothing in there can be scripted...
Possible solution is:
When your container data is in the same folder of your database, just Zip that folder in stead of taking compacted copy.
Give that to your end-user.
Let them unzip the folder... and ready!
I confess I'm feeling shaky when it comes to filemaker's managed storage. Can one just pick up/zip up a file with its managed storage and move it about like that? How is this normally handled with third party server solutions like Point in Space? The only time I've fooled around with those services I've uploaded a single file, then unpacked it once it was on the server. I wonder- do those services normally allow you to upload a folder (the database with its managed storage)? I'd hugely appreciate pointers to any literature on the matter as I've been coming up empty in that regard.
As long as the containers are in the same folder(or subfolder) this should work fine.
But maybe you should contact Point in Space about that.
I just thought about another solution, fully scriptable...
Why not making for every container field, a self contained copy of it next to it.
When you have the need to transfer the file, copy all the data from the external containers to the 'internal' containers.
Afterwards just do the opposite... fully scriptable and in fact about the same what FileMaker does when makin a file self-contained.
Clever! I may just do that. I'll certainly be testing it out. Thank you!