Database Reference
In-Depth Information
After the conversion is finished, open the Conversion.log file to make sure there were
no problems in the new file. You'll find the log file in the folder where you stored the
converted file. Double-click to open it in your usual word processing program.
Fig-
ure B-4
shows a sample log.
Figure B-4. The Conversion.log file is a record of what happened during conversion. Don't panic if
you see what looks like a column of errors in your file, as shown here. That column that looks like
-0700 is actually part of the timestamp in column one. The error column is that soothing series of
0s showing a successful conversion. If you have any doubts, just read that last column entitled Mes-
sages. Or you can open the log in a program that supports tab stop alignment or tables and then
format the file for better legibility.
Most of the lines in the log will show that the conversion of each item was successful. If you
used a table with invalid field names (maybe they contain a “+” or another invalid character),
the log will let you know. If you do see error codes, go to FileMaker Pro Help for more in-
formation. On the Home page, click the Reference link and then the FileMaker Pro Error
Code link to see the list. Most of the time, the Message column will tell you what you need
to know to fix the problem.
In most cases, you can fix the issue in the converted file. If you're doing a test conversion,
fix a few problems to see how complex they are. You may decide that it makes more sense to
fix the problem in your pre-12 file and then do the conversion over again.
Troubleshooting Conversion Problems
Most conversions are quick and easy. But if you're having problems, here are some things to
check:
