3 Replies Latest reply on Nov 5, 2014 1:29 PM by philmodjunk

    Alias for database files in Yosemite not working

    intex

      Summary

      Alias for database files in Yosemite not working

      Product

      FileMaker Pro

      Version

      12, 13

      Operating system version

      10.10 Mac OS X

      Description of the issue

      So far users of our runtime based apps could move their database files away from the runtime to the documents folder for example and then generate an Alias, move that back to the runtime and cut off the "Alias" part in the name and the runtime would find the database.

      This does not work anymore in Yosemite and is a major issue, since normally the OS and users would expect to have the program (runtime) in the program folder and their data (database file) in their documents folder or the library folder. With the use of an Alias this was possible, but isn´t anymore.

      Steps to reproduce the problem

      In Yosemite:
      - Move the database file away from the runtime app
      - Create an Alias of the database file
      - Move the Alias back to the runtime app
      - Remove " Alias" from the name of the Alias, so that the name is identical to the database file itself
      - Start the runtime app - it will not find it´s database.

      Expected result

      It should find the database. It worked for years like that. Tested it with FM12 and FM13 based apps on Mac OS X 10.8.5 for example and it works.

      Actual result

      FM12 and FM13 based apps don´t find the database in Yosemite.

      Exact text of any error message(s) that appear

      Primary file missing

      Configuration information

      Standard iMac

      Workaround

      None so far.