Optimized Container Storage
While FileMaker may promote the low-code/no code aspects of FileMaker Pro, there's a lot to be said about knowing how to design a great system as opposed to thinking you'll end up with one by default. Especially, one which will perform under load and scale to the degree which FileMaker can.
This type of knowledge is learned and simply won't come out of the box when you just start adding fields to your database. If you need to store images, or any type of heavy media, then it may not be a good idea to carelessly start throwing container fields into your tables. In fact, there's a whole bunch of details to know about FileMaker and how it transfers data on a record level basis. As well as knowing what can be done to optimize your storage of container based data.
While you'll want things to be easy for your users for adding media, and you'll also want to build a system which will be easy to maintain and update. That's what this video is all about. An optimized approach to container storage and making it easy on yourself when you're going to be working with these types of solutions in the future.
Comments
Helpful video!
Helpful video! Especially the part with the "false" filter is a cool possibility. Thank you ;-)
Container storage
It would have been nice to show how to open the container content via double click
Peter Cortiel
No Foreign Keys
Hi Matt, great video. Many thanks.
I have a question. You create related records, but they have no foreign key. You write the related image-records Id’s into the main record with a multikey field.
Why? Normally you have in each child record the key of the mother as foreign key. Is this done for performance.? Would otherwise the info of the child records be loaded regardless if displayed or not? I do not think so.. ?
External Storage Question
Matt,
Very cool stuff! I have used container fields and often wondered about how to do updates to the database when using external storage for the images. Just wondering what would happen if using only the FileMaker standard way of setting up external storage. Meaning leaving the external storage files on the client computer and taking the database offline, sending it to a developer for an update and then reinstalling the database to the same location on the client's computer. Do you think all the links, etc. would still work? If not, then I assume that your techniques in this video would solve that problem.
Thanks for the great demo,
Rick
Error Message
Hi Matt, Always great videos.
I'm getting an error when I try to add images "Can not write file to the external storage."
I have all necessary permissions and even created my own folder using the defined path.
I'm running on a MAC and FM 18
Error Message
Hi Matt, Always great videos.
I'm getting an error when I try to add images "Can not write file to the external storage."
I have all necessary permissions and even created my own folder using the defined path.
I'm running on a MAC and FM 18
Tried again, works now?
I downloaded the demo file and its all good....? Cant say why?
But Thanks!
Name list portal on user layout
Hi Matt, very helpful.
If I was to think this as a DMS solution, the user would usually have a list of the names of the files related to his record. If this was to come from a portal that is linked to the image database, that would load overhead as well, correct?
So the least overhead would be by linking that image key to a descriptor table that has the foreign key of the image and some kind of "this is the name of the file" and further lightweight information?
That could be done via the script trigger to clear the generate global correct?
Or is this too much?
Thanks for your reply
Cheers
cateringtraveller
Logging file path of dragged file
Hi Matt, another question:
Is there a way to capture the path of the dropped file (from where it was dropped)?
I would like to delete the file after successfully moving it to filemaker.
Cheers and thank you
cateringtraveller