Filemaker server 11 tutorial for mac#
Filemaker server 11 tutorial install#

You either need to unzip and copy from a Mac or download the. However, you can't unzip the Mac plugin on Windows or Linux and have it still work on the Mac. The easiest way is to drag and drop the plugins into corresponding container fields, one for each platform. Getting the Plugin into a container field This could be a single record Plugins table you create just for this purpose, or could be global fields that you set in the file when it's not hosted.Īll of the scripted methods require that the BaseElements plugin is first inside a FileMaker container field. So one for Win32, Win64, Mac and Linux, or only one if you are only ever on a single platform. If you're starting from scratch to build this yourself, it's not complex, but there are a few steps.Ĭreate a FileMaker file ( or use a table in an existing file, or create a new table) with container fields to store all of the versions of the plugin you need to install.

Filemaker server 11 tutorial install#

You can use a script that runs via the On First Window Open trigger, to check for the latest version and install it if required. The scripted install is the best way to keep plugins up to date on any system that is being used constantly and where you want to check that the plugin is active before you let a user do tasks that require the plugin. Recommended : Scripted Installation for Client or Server There's also different locations on server for different functionality, so a plugin that does a calculation that displays in WebDirect will need to be installed for that, and will be a different location than one for Perform Script on Server scripts.Īlso when you use plugin functions inside stored calculation fields, these can often be evaluated on the server, so the plugin needs to be installed there too. And some behaviours, especially around file paths, will be different on each platform.

Filemaker server 11 tutorial for mac#

Each FileMakerPro client will need to have a copy of the plugin installed locally for them to be able to use plugin functions inside scripts and calculations that run on the client.Įach FileMaker Pro client with a different OS needs a different plugin - so there are different files for Mac vs Windows for example. You can install plugin on FileMaker server - this doesn't not do anything for FileMaker clients being able to use plugin functions though. The first thing to understand is the difference between a server and client install. fmplugin file, now what do you do? Server vs Client installs You've downloaded the plugin file, and got a.