User manual

Converting FileMaker databases from previous versions 95
Note If you later need to convert the same files again, make sure you
convert the files into an empty folder; move or delete any files from
the previous conversion attempt, or create a new folder for the next
conversion. This prevents converted files from being renamed
during the next conversion which could cause file references to
convert improperly.
Reading the Conversion.log file
You should open and read the Conversion.log file after converting
one or multiple files. It lists the conversion status and possible
problems found during conversion, such as fields with invalid
names.
The log file is created in the same folder as your converted files. If
you used the multi-file conversion method to convert more than one
file at a time, the Conversion.log file contains information for all the
converted files.
In most cases, you can correct problems in converted files. If the log
file indicates that there is a problem that would be complicated and
time-consuming to fix after conversion, you may want to try
correcting the problem in the original file using a previous version of
FileMaker
Pro, and then convert the file again. Detailed descriptions
of the log entries that may appear are available in chapter 3 of
Converting FileMaker Databases from Previous Versions.
Important The Conversion.log file may not indicate every item in the
file that needs to be corrected. Before you begin using a converted
database solution, you should test it thoroughly to make sure every
aspect has converted successfully. For example, make sure every
script works as you expect, and that accounts and privilege sets
provide the required file security.
Solving basic conversion problems
Here are some suggestions for correcting problems that could occur
during conversion.
FileMaker Pro 7 can’t open my file
FileMaker Pro 7 can’t convert databases that were created with
FileMaker
Pro 1x or 2x. For more information, see the next section,
“Converting FileMaker Pro 1.x and 2.x databases.”
My file didn’t convert properly
1 If you are converting a copy of a file, make sure that the original
file was closed before you copied it. Otherwise, the copy will not
convert correctly.
1 Check the Conversion.log file located in the folder with the
database you are attempting to convert. For more information, see
the previous section,
“Reading the Conversion.log file.”
1 Try recovering the file first using a previous version of FileMaker
Pro and then convert the file again.
I received a consistency check or auto-repair message when I
opened my original file using my previous version of FileMaker Pro
Try recovering the original file using your previous version of
FileMaker Pro. Then open the recovered file using the same version
of FileMaker
Pro, close the file, and then try converting it with
FileMaker
Pro 7.
The converted file won’t accept my password
Passwords are case-sensitive in FileMaker Pro 7. Make sure you
enter your password exactly as it was created in a previous version
of FileMaker Pro. If you are the owner of the original file or the
database administrator, open the original file using a previous
version of FileMaker
Pro, and look at the password in the Define
Passwords dialog box. If you are not the owner of the file or the