Running into a bloat issue using FMPv9.3 and linking pdfs to records using a container field. Does it make sense to see a MBs worth of space being used to just link a pdf to a container field? And, what if a file is hosted? It seems the opening and closing helps recover some of the space that was used to create the link. But if the file is being served, there is no regular open/close.

We ran into a problem with v6 and the 2GB size limitation. Only 1400 records with linked pds filled that 2GB up. Network Admin is concerned about file size, and backups and using up that much space for "nothing".

Thoughts?

Below is what we are seeing when linking/embedding pdfs and xls.

Initial file size is 152.322 MB, embedded a 54 MB PDF resulting file size is 297.082 MB file size = 145 MB bloat.

Closed and reopened the DB. File size reduced to 214.355 MB = 83 MB reduction.

Created new record, linked the same 54MB PDF, display as icon. File size increased to 217.399 MB = 3MB bloat.

Closed/reopened DB = file size reduced to 215.871 MB = 1.528 MB reduction.

Then I embedded a 4.824 MB XLS. File size increased to 229.158 MB = 14MB bloat.

Closed/Reopened DB and file reduced to 221.560 MB = 7.598 MB reduction.

Linked the same 4.824 MB XLS, display as icon. File size 222.072 = 512 KB Bloat.

Closed/Reopened DB. File size 221.810 = 262 KB reduction.

Don't store the files in the database you are a perfect candidate for

360Works SuperContainer

http://www.360works.com/supercontainer/