User manual

Table Of Contents
Chapter 7 | Using FileMaker Pro Advanced 127
Organizing solution components
When you bind your files into a runtime solution, the Developer Utilities create a new solution
folder and place the runtime application, the bound primary and auxiliary database files, and an
Extensions folder inside it. For Windows runtime solutions, there are also required Dynamic Link
Library (DLL) files.
Note When you move multiple files into one folder to create a runtime solution, be aware that
your internal links are affected. For this reason, every data source must include a path that is just
the filename of the file being referenced. Although the runtime application will check other data
sources, it will then be able to find the file in the same folder in which it resides. You can still keep
any absolute or relative paths in the same data source reference in case the files are also used in
FileMaker
Pro or FileMaker Pro Advanced.
Important These files and folders must not be renamed.
If your runtime solution requires custom files, you should provide the files with the runtime files.
The location of plug-in files depends on whether plug-ins need to be available to multiple versions
of FileMaker
Pro.
If a developer uses a font not found on a user’s system, the runtime application will make a font
substitution. If a font is included with the runtime, provision should be made for its installation
through the installer program.
Testing before and after creating your solution
You should verify the functionality of your solution by testing it thoroughly before and after you
customize it with the Developer Utilities.
To ensure the quality of your custom solution:
1 Verify every function and option in your solution. If you’re developing a solution for both
platforms, test it in both Windows and OS X.
1 Make sure your runtime solution does not use a standard FileMaker Pro feature that is hidden
or disabled in the runtime application.
Windows solution folder OS X solution folder
Runtime application
Runtime application
package
Bound primary and
auxiliary solution files
Bound primary and
auxiliary solution files
Extensions
Dictionaries
DLLs generated during
binding
Example of Windows and OS X solution contents for distribution
Extensions
Dictionaries
Language
resource folders