لطفا منتظر باشید ...
Consolidating Multiple Related Files
A database solution with one or more smaller databases (such as lookup tables for Zip codes) is a prime candidate to be combined into one file with several related tables. You can convert the largest (main) database using the conversion procedures discussed earlier. Once you've done that, you create new tables within the main database that can hold imported data from the old lookup files.In this example we add a Zip code lookup table to a sales database and import the records from the old file.
To consolidate related files into one new database
1 .Convert the main database file to be recreated into FileMaker 7.2 .In the converted file, choose File > Define > Database (Control+Shift+D/Command+Shift+D). In the Define Database dialog box, click the Tables tab.3 .In the Table Name box, type a name for the new table. (We use Zip Codes.). Click Create (Figure 15.13).
Figure 15.13. Create a new table within the database to eliminate having to open separate files.
[View full size image]
Figure 15.14. Using the same field names as the old database makes the import process easier.
[View full size image]
Figure 15.15. To be able to import records, you have to create at least one layout using the table.
Figure 15.16. A column list is the easiest format for browsing a database with only a few fields.
Figure 15.17. There are only three fields in the table, so they will easily fit on the layout.
Figure 15.18. Field names are matched by default in the Import Field Mapping dialog box.
Once you have recreated an external file in a new table, you must update any relationships that used the old file to use the new table.
To manually change converted files
1 .Choose Define > Database (Control+Shift+D/Command+Shift+D). In the Define Database dialog box, click the Relationships tab.2 .Double-click the = icon that connects the table from the older external file. In the Specify Table dialog box, choose Current File from the File: drop-down list if it is not already selected. Click the new table in the list, and provide a name in the Name of Table Occurrence. Click OK (Figure 15.19).
Figure 15.19. Choose the current file and then choose the recreated table within it.
If your old database had scripts with steps that called scripts to navigateto another database that you have recreated as a table, you'll have to change the script to go to another layout in the current database.
To update scripts in converted files
1 .In the main database, choose Scripts > ScriptMaker (Control+Shift+S/ Command+Shift+S).2 .In the Define Scripts dialog box, double-click the script that calls the old external script.3 .In the Edit Script dialog box, click the step that calls the external file. Click Clear (Figure 15.20).
Figure 15.20. Delete the Perform Script step before replacing it with a Go to Layout step.
[View full size image]
Figure 15.21. Choose the layout for the table that replaces the external database's layout.
[View full size image]
TipsTo save time when converting large files, skip index creation. The conversion will go considerably faster. Indexes will be recreated automatically as users access data with Finds.Once you've replaced all old relationships to external files with new relationships to internal tables, it's a good idea to delete references to the old external file in File > Define > File References. Cleaning up makes it easier to see and troubleshoot relationships and helps to uncover hidden references to the old file.
Status Functions to Get Functions
What were called Status and Text functions in previous versions of FileMaker are now called Get functions. When converting a database, all instances of old Status and Text functions are updated to the corresponding Get function.Here are some of the major old functions with their new syntax.
