لطفا منتظر باشید ...
Cleaning Up After Conversion
No matter how carefully you clean up and analyze in advance, it's hard to recreate a perfect database. Chances are, either you've missed something in your preparations, or FileMaker 7 has done something you didn't expect in the conversion process. Post-conversion, you owe it to yourself and your users to do a complete check of every aspect of the files. In particular, you need to check calculated fields and scriptsthe prime places for anomalies to hide. Because FileMaker 7 and earlier versions are not compatible, you can run them simultaneously. Open the pre- and post-conversion files and compare them side by side.
To check data and layouts
1 .Open the old file in the previous version of FileMaker and the new file in FileMaker 7.2 .In the newly converted file, choose View > Browse Mode (Control+B/ Command+B).3 .Compare the number of records in each file. They should be the same.4 .Compare the data in each field against the data in the old file. In large files, it may be impractical to compare every record. You canspot-check a number of different records.5 .If you find major discrepancies in the data, toss the new file and run the conversion again.6 .In the new database, choose View > Layout Mode (Command+L/Control+L). Check each layout, making sure that all of the fields appear. Check the format for each field: text alignment, number format, and so on (Figure 15.22).
Figure 15.22. Text alignment is sometimes inconsistent in converted files.
[View full size image]
To check calculations
1 .In the newly converted file, choose File > Define > Database (Control+Shift+D/ Command+Shift+D).2 .Click the Fields tab. Click the Type column header. This will sort the fields by type. Scroll down to the Calculation fields (Figure 15.23).
Figure 15.23. Clicking on the Type column header sorts the field display, putting fields of each type together.
[View full size image]
You should test all of your scripts after converting and before deploying a database. If you have any scripts that might result in data corruption if they run in unexpected ways, make a copy of the entire new database setup, and test your scripts on the copy. If something goes wrong, you haven't created work for yourself.
To test scripts
1 .Choose Scripts>ScriptMaker (Control+Shift+S/Command+Shift+S).2 .Click on each script and then click Perform (Figure 15.24).
Figure 15.24. You can perform a script that isn't listed in the Script menu by clicking the Perform button in ScriptMaker.
