For the first database, there was one container field in one table with 68K records. It then compressed the database to reclaim the unused space.
Filemaker baseelements list folder on mac remote path pro#
FileMaker Pro started moving the documents in the container fields to a folder called “Files” outside the database. (You could also use BaseElements or Inspector to search by field type.) For each container field, I changed the storage option to “Store container data externally” under Field Options.įinally, I closed the Manage Database window to save the changes. Next, I went through each table looking for the any container fields. Next, I opened the database and sorted the field list by “field type”. Fortunately, FileMaker 12 has a new feature called Enhanced (or external) Container Fields to address this.įor each database, I converted it by dragging the file onto the icon for FileMaker 12 and going through the automatic conversion process. The disadvantages of a large database in FileMaker are several including slower performance (more data to push over network), lower productivity (long wait times during backups), and greater risk (more susceptible to corruption in the event of a crash).
The result in each case was database bloat-a file size much larger than necessary (1GB or greater). Both customers were embedding documents in the database by inserting them into container fields. Recently, I converted two customer databases from FileMaker 11 to FileMaker 12.
0 kommentar(er)
