Proper Image Handling
Just because you can click the Create button to add a new container field doesn't mean you should do it. In fact, you might want to consider never adding a single container field to your main solution's tables. "Really?", you ask. Yes, because there are many advantages to segmenting a solution into multiple distinct parts. Most media, images, video and audio, is considered "heavy data" and that data comes with a big cost.
It may be that you're unfamiliar with how you can best structure your data within FileMaker. With images, you're often better served by handling that data in a very specific and dedicated way. This video, and the associated technique file, shows you how to approach the situation of handling images. It also addresses the display of those images. For the sake of images, you certainly need to see the image for the value it provides. However, you rarely need to transfer the full image which was captured or imported.
Watch this video in order to gain a full understanding of how it may be best to both store and view your images within a FileMaker solution.
Comments
Extra file for media
Thanks for the video. A useful capture techique which I have used for years. However, I see no advantage in using a separate file for media, in fact I almost never use multiple files in a solution anymore. Primarily because one needs to replicate the security schema across all files which can be a pain with many local accounts or privilege sets. Rather, I have all the media in a separate table within the main file, but I always use external storage as not to bloat the database file.
Same for me
Although I do have some solutions which use multiple files the advantages of having it all in a single file are larger. Not only the security. What to think of your theme? Since it’s not possible to share those resources over multiple files it’s easier to keep it all in a single file.
Gerard van der Wolf