Developer’s Guide

3-8 FileMaker Pro Developer’s Guide
1 Test your solution with actual data. This is especially important if end
users are upgrading from earlier versions of the runtime application
and need to import data into new solution files.
1 Make sure all the auxiliary files and DLLs (Windows) are present.
1 Show your solution to intended end users to uncover any
usability issues.
1 Install your bundled solution to a completely different computer to
verify that all the files associated with the primary file can be found.
1 If you’re removing master access or assigning passwords, test all
access levels. Make sure your end users are aware of the level of
access you’re providing. See “Use custom ‘About’ script” on
page 2-10 and “Policy on decoding and repairing passwords” on
page 3-6 for more information.
Important You should keep an unbound version of any solution files,
especially if you’ve removed master access.
Design tips for cross-platform solutions
If you’re developing a solution to be run on both IBM-compatible and
Mac OS-compatible computers, there are many issues that require
planning and consideration (for example, font technology, colors, and
design conventions). For information on creating cross-platform
runtime solutions, see “Binding cross-platform solutions” on page 2-20.
Fonts
To ensure a consistent look for files across platforms, try to use the same
font technology, for example TrueType. It is best to use fonts with
identical names, styles, and metrics on both platforms. When fonts used
to view a file are different from the ones used to create the file, there can
be problems with word wrap and placement.
Most font vendors supply Windows and Mac OS versions of the same
font. Contact your font vendor for more information.
When you move a file from one platform to another, if the font used to
create the file isn’t available, another font will be substituted. In
FileMaker Pro 4.0 for Windows, you can specify how fonts are
substituted in the Microsoft Windows Registry Editor.