Thoughts on separate tables for IMAGES and DOCUMENTS?

[dmontano]

Hello all,

I could use some help "analyzing" this:

I currently have a ONE table called DOCUMENT. This one table was intended to hold any IMAGES (graphic, photo, diagram, etc.) and any DOCUMENTS (spreadsheet, MP3s, manuals, etc.). I would then relate the DOCUMENT table to any other table in the database that required the storage or access to DOCUMENTS.

FIRST OBSERVATION:

I have noticed with a differentiation between two "classes" of documents within FileMaker options:

For example: Optimize for IMAGE or INTERACTIVE CONTENT.

SECOND OBSERVATION:

An average User (including myself) could benefit from seeing a separated "view" of IMAGES (like photos, diagrams, etc.) from DOCUMENTS (spreadsheets, manuals, catalogs, etc.)

IMPLEMENTATION THOUGHTS:

How to provide this separation with the ONE table I have now? Create a field that distinguishes between these two "classes"? While this could help satisfy a desire to separate the two classes on the interface; does it provide a means to set different optimization properties within FileMaker? It seems as if I would need to create TWO containers in the DOCUMENT table with show/hide conditions based on the incoming document "class".

Or, I create two separate tables: one for IMAGES, the other for DOCUMENTS (in a more traditional text-with-graphics sense).  Which brings up a third consideration about VIDEO type of documents and if they require unique handling/optimation just as the other two classes.

Any thoughts are appreciated.

[comment]

Just a random thought:

Whether a field is optimized for static or interactive content is a matter of formatting the specific instance of the field on a specific layout. You could have two separate layouts showing the same field optimized differently. Or two different instances of the same field on different panels of a tab/slide control. Or even just hiding one of them conditionally.

 

[dmontano]

Thanks Comment,

I'm going to stick with the one DOCUMENT table, add a field in DOCUMENT to "type" the file "class", create two container fields optimize by "class", and show / hide based on class too.

Without investigating right now, I also believe there are choices when exporting or maybe saving as ... when one needs to obtain a copy: not sure off top of my head.

I appreciate your help.