1 Reply Latest reply on Feb 8, 2009 6:49 AM by davidanders

    best practices for container field file paths?



      best practices for container field file paths?


      I'm going to be using a lot of container fields with paths to PDF files.  Currently I keep all the referenced PDFs in a single folder.


      What is the best approach to enable me to move this database to another computer someday?  (I don't want to store the PDFs in the database.)  My understanding is that the file paths are "hard", meaning they wouldn't work if the database and PDF folder were moved to a different account/machine.


      Is there a way to globally change all the container field file path references in the database to reflect the new location of the PDF folder on a new machine? 


      Or is there a variable in FM that can be set to "~" so that the PDF folder would be found in any account that it was located in?

        • 1. Re: best practices for container field file paths?

          When importing references to the PDFs, the reference contains path and filename.

          Calculated field to extract path 

          Calculated field to extract filename


          When files moved, change path

          calculate newpath-filename 

          replace container with reference.


          This can be granular down to path\folder, so you could move selected files to a new or enclosing folder and change the reference.