I'm looking for advice regarding strategies for storing photos/scans within my database. Currently, I'm of the mindset that I would prefer to have a single 'container table' that is used throughout the database where needed. This table would have a few identifiers, which autofill based on where (as in from which layout, or where on the layout) the container is populated. Then, there would be a single layout where all photos/scans could be browsed/filtered/etc based upon those identifiers. 

First question, is this design good practice or should I reconsider my approach? Please note that for my purposes a container is not always necessary for every record (i.e. some records will have photos attached to them, and many others will not), and some records will need multiple containers (a record can have more than one photo attached to it). 

Second, in the case this is good practice, are there any examples available on how to best implement it?

I really appreciate your time, please let me know if further clarification of my question is necessary. 

How about a separate file?

 

 

Thanks bcooney for the advice, I'll have a look at this option! Hadn't thought about backups, so having the external file seems a really good solution. Will still need to figure out how to make it work with my layouts so that the appropriate identifiers will populate whenever a photo is added. 

Thanks!

Not sure what you mean by identifiers. Perhaps you mean the foreign key? Since this table ( maybe in its own file) , can relate to many entities, perhaps add ParentEntityId and EntityTypeId?

If you use UUIDs, it is highly unlikely that any parent from across all entities that relate to your container would have the same uuid. 

EntityType table would have a row for each possible parent entity. For example, “Invoice” is entitytype 1. We typically don’t use uuids on a lookup table. 

Hi Eli,

Whether you store your containers externally or internally in the file, you can have several tables share that Container file.  Any information you include in in an auto-enter can be transferred to the Container table when you insert the photo or file into the container (please see attached).

Hi Barbara!  Nice to see you again!

Added:  If you are really worried about duplicates, you can include the table in each Parent table.  Create an unstored calculation and include it in the relationship instead but most feel that isn't necessary.

 

DataWithContainers.fmp12

Edited March 22, 20196 yr by LaRetta