#FILEMAKER SERVER 14 GETTING STARTED PRO#
#FILEMAKER SERVER 14 GETTING STARTED CODE#

PatternCount ( Get ( HostApplicationVersion ) “Server” ) will get all the information that you’re looking for.Ģ. Get ( ConnectionState ) would return a 1 if the file were being hosted by a client via peer-to-peer, thus not entirely useful, and not really necessary. Marc Berning Posted on 4:05 AM - July 26, 2016ġ.

#FILEMAKER SERVER 14 GETTING STARTED CODE#

Just insert some code like this into your script and you’re off and running… on server! The beauty of this is that you can use PSoS when it’s available, but still run just fine when it’s not. If the file is not hosted, or is not hosted by a version 13 or higher server, then it will also skip the steps to call itself via PSoS, and the script just runs the rest of the procedure locally. Now the next time it runs (on the server), it will skip to the actual steps of the script we want to perform. If it is, then the script will recursevely call itself again using PSoS. Once it’s determined that the file is hosted by a version of FileMaker Server that can use PSoS, the script needs to know whether it is itself currently running on the local machine. Next, it needs to determine what version of FileMaker Server is hosting the file (using Get (HostApplicationVersion) ), and if that version is one that can handle PSoS (using PatternCount to look for the version numbers we require: 13 or 14). The specific code is shown below, but it basically works this way:įirst, the script needs to determine if the file is actually hosted (using Get (ConnectionState) ). While working on our second FileMaker module, fmRecentRecords, we perfected a neat scripting trick for automatically running a script on a server, whenever possible. The script has to be compatible with PSoS (and set up to run that way).The server that hosts it must support PSoS (v13 or v14).You have to be running a hosted FileMaker database.Of course, you can’t use “Perform Script on Server” (PSoS) if you don’t have the following three conditions present: So, it’s nice to perform a script on the server whenever you can. Performing certain scripted tasks on the server is also much, much faster in many cases. Tasks for which a user might otherwise have to wait to complete can be accomplished in the background without causing a delay.

#FILEMAKER SERVER 14 GETTING STARTED PRO#

The ability of FileMaker Pro to perform a script on the server instead of locally on the client’s machine is a huge potential boon for productivity.

Filemaker server 14 getting started