Data Separation | | Filemaker |
After a database goes "live", methods must be considered and selected for releasing programming modifications and updates. When changes are made offline without data separation, hours are spent (and paid for, by the client or employer) on imports that could have been handled within a few minutes had the data file(s) been separated from empty interface, logic, and presentation files, and upgraded by simple replacement of the empty files. The alternative to frequent imports in non-separated files is risking data to program changes made and tested in files with "live" data.

Via David Anders