Help

Creating a database
F
ILEMAKER PRO HELP 213
7. Create a start-up script that references the above scripts, in their script order, when a user
opens the database.
Notes
• Clients must be running FileMaker Pro 12 or later to update plug-ins using this method.
• For plug-ins to install, the Allow Solutions to Install Files option must be selected in the
client’s Plug-in preferences. See
Setting plug-in preferences.
• If a plug-in has been disabled in the client’s Plug-in preferences, it will install but will not be
accessible until it is manually enabled by the user.
• Only one plug-in can be stored in each container field, but you can view all plug-in
information by creating multiple plug-in container fields on a single layout.
Related topics
Creating custom plug-ins
Installing plug-ins
Get(InstalledFMPlugins)
Install Plug-In File
Plug-in update example
The following example compares the version of an installed plug-in to the version located in a
container field in the FileMaker Pro file and updates the plug-in, if necessary.
1. In the solution file, create a table named Plugin Update to store plug-in information.
2. Define the following fields:
3. Create a layout named Plugin Update Information and add to it the fields you defined in
step
2.
4. Create the following script and name it Install Plug-in:
Set Error Capture [On]
Install Plug-In File [Plugin Update::Plug-in File]
#
#Deal with errors
If [Get(LastError) ≠ 0]
If [Get(LastError) = 3]
Show Custom Dialog [Plugin Update::Plugin File & " could not be
installed.
Field name Field type
Plugin Name text
Required Plugin Version number
Installed Plugin Version calculation (unstored). For example code, see Client plug-in
version calculation.
Installed Plugin State calculation (unstored). For example code, see Client plug-in
enabled state calculation.
Plugin File container