5 Replies Latest reply on Nov 14, 2016 6:52 PM by BruceRobertson

    Extra External Tables

    keithstehlik

      I am cleaning up a solution that is about 15 years old. It was originally a collection of a whole bunch of databases. It has been redone so there are only two databases and a sql database. The main filemaker database is 'JobTicket' and the second is 'Separations'. Both of these are hosted on FileMaker Server. When I  look at Manage External Data Sources on the main file it looks like this

       

      There are 4 separate links to the 'Separations' database. What is the correct one to use that looks only at the filemaker server instance that the main database is using.

       

      I am also setting up another fileserver for another plant with these same databases and they seem to open the 'Separations' database from the wrong server at times

        • 1. Re: Extra External Tables
          wimdecorte

          We can't tell from the screenshot since each file reference can actually contain multiple lines and some of those may be the correct ones too.

           

          The correct format is the one for #3 with just the "file:" prefix

          • 2. Re: Extra External Tables
            OCDilla

            Seperations 3 will open up the file Seperations that is in the same folder/server as the primary file.

            • 3. Re: Extra External Tables
              keithstehlik

              Thanks

              I deleted all but the one that was file:Separation

              It broke a few things that were somehow point at the other ones but I getting thru most of that pretty easy

              • 4. Re: Extra External Tables
                philmodjunk

                Once upon a time, direct access to and management of external data source info was not possible in FileMaker. The application managed the links internally and we had to live with whatever external data source entries thus produced. However, FileMaker was apparently listening when we complained about the problems that we were encountering due to the inability to control these settings and they introduced this tool in one of the new version releases.

                 

                When I converted a copy that originated from those days to FMP v 10 and opened up manage | External datasources, I found an awful mess of multiple duplicated data sources with multiple entries in most of them that makes what you have here look very clean and simple in comparison.

                 

                But I found that a Database Design Report (today, I'd use Base Elements or a similar tool), was invaluable in tracking down and updating data source references so that I could effectively clean up the external datasources to just one for each file.

                • 5. Re: Extra External Tables
                  BruceRobertson

                  It looks like it's too late now. But really, the thing to do BEFORE turning off all the others, is to find the scripts and table occurrences that point to the others; and point them all to ONE data source. THEN delete all the alternate data sources.