User manual

Converting FileMaker databases from previous versions 97
1 Custom user dictionary: When you convert a database file that
references a custom dictionary file, the converted file continues to
look for the dictionary in its previous location. If you move or delete
the dictionary from that location, the converted file will no longer
have access to information in the custom dictionary. This could
happen accidentally if the original custom dictionary file is located
in the previous FileMaker Pro folder and you later uninstall the
previous version of FileMaker Pro.
To preserve a custom user dictionary, move the dictionary file to
your My Documents folder (Windows) or you home folder
(Mac
OS). Then, after converting a database file, specify that it use
the dictionary file in the new location. For more information, see the
information on selecting spelling dictionaries in Help.
Print Setup script step stored setup options (Windows)
The Print Setup script step is able to store and use custom paper
options that can be recalled when you run a script. This allows you
to use a script to print a particular layout with different paper options
— for example, to print labels or print on a pre-printed form.
FileMaker Pro 7 uses a new format to create and store options in the
Print Setup script step. The new format is not compatible with the
format used in previous versions of FileMaker Pro, and FileMaker
Pro 7 cannot completely convert stored setup options in previous
files to the new format.
After conversion, if you want to edit stored setup options for the Print
Setup script step, you may need to remember what the settings were
so that you can enter them again properly. You may want to view the
options in the previous, unconverted file so that you can enter them
correctly.
Switching windows in scripts
When necessary, previous versions of FileMaker Pro would
automatically change the active window after running a script. This
automatic windowing behavior is no longer supported because
FileMaker Pro
7 supports a new Select Window script step, which
script writers can use to set the active window.
To emulate the behavior of previous versions, during file conversion
FileMaker Pro
7 automatically inserts Select Window script steps
after certain Perform Script and Go to Related Record script steps.
To achieve the windowing behavior you want, you may need to
insert or delete Select Window script steps.
Boolean functions and find requests
Because FileMaker Pro 7 does not recognize previously supported
alphabetic characters in a number field as numbers, some logical
functions that return Boolean true/false results may return the wrong
results. Also, some find requests for Boolean content may return
different results in FileMaker Pro 7 than in previous releases.
The following table shows how Boolean results can differ in
FileMaker Pro 7 compared to earlier versions.
If you have used “Yes” or “T” or other text to mean true in number
fields, Boolean calculations relying on these characters will not
return results consistent with previous versions of FileMaker Pro.
Number field content
In FileMaker Pro 7,
evaluates to
In FileMaker Pro 6 and
earlier, evaluates to
blank field False False
0 False False
1 True True
True, Yes, Y, y, T, or t False True
False, No, N, n, F, or f False False