2 Replies Latest reply on Jun 10, 2014 6:23 AM by Oliver_Reid

    ESS TO relationships break when MySQL db is Copied to a new Server?


      How does FM remember its Mapping of MySQL fields?



      I am moving a Mysql db to a different server and find my FM ESS TO's lose of which field is which w.r.t. relationship links in FM between ESS TO's i.e. the wrong fields are connected when switching the FM app to use the new DSN


      I have moved the db Using Navicat's dat transfer facility, which in fact drops and recreates esch table.


      In cases - I think where the MySQL field order has changed since the FM mapping was done, the new db fields do not line up.


      If anyone has had expierence working around these issues, or under the hood knowledge as to how FM maps to SQL fields, I'd appreciate any insights.

      or actual experience, please (resyncing ESS tables does not help)


      I have tried a Navicat Backup and restore to the new db, but that also involves dropping and recreating every table.

        • 1. Re: ESS TO relationships break when MySQL db is Copied to a new Server?

          Oliver, I've experienced similar type situations, and have corrected it by adding a second data source ( File > Manage > External Data Sources ), and switching the TO to that second source, keeping the same TO name, and then saving.


          It's inconvenient, but filemaker seems to cache the ESS connection settings and schema data on a deeper level.


          The sync button will only pull the schema data from the source it's connected to, and I have previously proven in my testing that it caches the connection data in the relational graph, even if you change the ODBC DSN settings, and the data source information inside FM. The way around it was adding a second source, and changing all of the TOs.


          Offhand, is your OLD data source still available while this is going on?

          • 2. Re: ESS TO relationships break when MySQL db is Copied to a new Server?

            Thnaks Mike


            I will try that


            In My schema I am trying to have only one TO link to each ESS table, and any extar ESS  TO's based on the shadow table in FM rather than direc to the ESS table -- so I should only have to change teh TO once for each SQL table.


            I did make some progress by syncing every Table before creating the new copy of the database, but still some TO's were misconfigured.


            Your method will take longer (not much though) and if it proves 100% reliable that will be a relief.