3 Replies Latest reply on Nov 21, 2011 10:00 AM by philmodjunk

    Container links taking mega space



      Container links taking mega space


      We have several thousand pdf's stored on our server with only a link to each file stored in a container field for the relevant record. With each new link, FM is gobbling up server storage. Currently, without links, the entire FM database is around 700mb. With only file links and no actual images stored in container fields, the database is over 20gb & growing daily as we add pdf's to our server. 

      How can I store file links without taking up FM database space?

        • 1. Re: Container links taking mega space

          Are you sure you these files were inserted with the "store a reference" option?

          What you describe sounds like a physical copy of the file is being inserted into each container field.

          • 2. Re: Container links taking mega space

             Yes. Originally we stored the physical document in the container and changed it to only a link without a thumbnail view of the document to reduce file space. When you right click on the container in browse mode, the only option is to open the linked acrobat document. The following screen shot is the right click menu.


            • 3. Re: Container links taking mega space

              This actually stores a copy of the file as you appear to be using the Insert Object method supported only in windows via OLE (Object linking and embedding.)

              If you use Insert File and select the "store a reference" option in the dialog that appears when you select the insert option, you should see that your file size grows much more slowly as you add records and insert additional files.

              Note: I've found an article in the Knowledge base that indicates that OLE is on their "to be deprecated" list for future releases of FileMaker so you might want to transitioin away from OLE now be fore getting caught by suprise when upgrading to a newer version of FileMaker some time in the future...