1 Reply Latest reply on Jul 11, 2017 1:17 PM by mikebeargie

    Recreating file references for container fields

    ChristofferRexen_1

      Hello everyone

       

      QUESTION :

      Is it possible to recreate the file references, without moving towards an External Storage solution?

       

      Currently one of our customers still operate in FileMaker Pro 13, although with the all new FileMaker Pro 16, we advised to update.

       

      Now, the customer has some rather old databases which holds a large number of container fields.

       

      These container fields only holds a file reference, to a specific file (picture, pdf, spreadsheet, document etc.), but as most you know, this reference will vanish when updating a client to FMP 14 or above and making the transition, cause of the Path Syntax issue.

       

      FileMaker 14 and above started getting much more strict on the File Names and Paths that it will use.

      If there are any non-alphanumeric characters for instance.

       

      The files which are referenced too, are stored on the same Server as where the FileMaker (V. 14) Server is hosted.

      I fear that the problem truly lies in the folders, where the files are referenced from, e.g. One of many folders are named "ALOC A/S - SE VITEC ALOC A/S"

       

      QUESTION :

      Is it possible to recreate the file references, without moving towards an External Storage solution?

       

      On a sidenote:

      I looked into this article, but it's rather old and not really the case scenario, Recreating file references for container fields | FileMaker.

       

      Regards

      Christoffer

        • 1. Re: Recreating file references for container fields
          mikebeargie

          The reference values will always be stored and accessible via text after the conversion. You will just need a plan in place for your client if any of the references are broken.

           

          You could script something by searching for special characters in the reference path, then doing an "insert from url" calculation.

           

          The cleaner way would be to move it to external storage though, as filemaker will then reference things properly, not by a path that is vulnerable to breaking with special characters.