That depends on how you have container fields setup. They can either be stored internally in the database or externally.
If you have them set to be stored externally in could be in a few different locations depending on your settings. This may help answer your question:
Internally. If its internal where is it stored? Using fm11
1 of 1 people found this helpful
In FM11 and earlier, internal storage means the data of the actual file is stored into the container field (as opposed to storing only a reference to the file). That means the FM file size grows directly as the amount of binary data increases within containers. It all becomes part of the FM file itself and the digital data cannot be sorted out except via the field interface of the layout(s).
What do you guys recommend the best thing being when storing files. Is it best to store files on a separate file server to avoid increasing the size of the database?
What version of FM Server?
What kind of Hardware is it running on?
What kind of files?
How do they relate to the FileMaker Database?
Are you using Super Container by 360Works?
How big is the database?
A little more information will help you get the best recommendation.
While you pose good questions regarding where to store container field files in FMP 11, Nicole, and there are many good strategies with and without plugins, the "killer" feature of FMP 12 is the ability to let FileMaker handle this via "external storage." I've sold many clients on the upgrade to 12 on this feature alone.
Ann Arbor, MI
FMP Server 11 advanced Windows platform
The files are mostly going to be PDF's
They are contracts
We do have super container (Im not too familiar with super container and how it works) but for that field I dont think its linked to super container unless supercontainer applies to all containers in database. (Maybe someone can enlighten me there )
The database is about 615MB
I agree but unfortunately we arent upgrading till later this year.