1 Reply Latest reply on Oct 25, 2010 8:46 AM by philmodjunk

    Help with distribution and maintenance of multiple databases?



      Help with distribution and maintenance of multiple databases?


      thanks for your time...

      i created, somewhat by accident, a filemaker solution that i am now getting lots of demand to sell/support.

      i could really use some advice on the following:

      if i have, say, 20 clients, all running nearly identical databases, accessing them via IWP, how do i go about the process of upgrading?

      i develop on a local database, but is there a good process/philosophy for updating multiple databases hosted on filemaker server?

      any input on this would be great, as i am quickly becoming swamped, and am stressed about the support/upgrade process.



        • 1. Re: Help with distribution and maintenance of multiple databases?

          Two techniques:

          Split your system into two files: a data file that holds all your data tables and data level relationships such as those you need to support a calculation field that draws data from a related table and an interface table for layouts, scripts etc. The relationship graph on this second table uses external data source references to link to the data file. Since most upgrades invold only changes to the interface file, you can now distribute such changes and the user only has to replace the interface file with the updated copy.

          Write a script that imports all data from all tables in the old copy of your filemaker file into all tables of the new. Include script steps that also update the next serial value of all auto-entered serial number fields as well. This script can be devised so that the user simply clicks an update button, selects the original file in an open file dialog and then the script does the rest--this can even be left to run overnight with systems that have large quantities of data in them.