Confused by the options for 32 and 64 bit plugins in FileMaker 14? Andrew Duncan of Databuzz spells it all out for you:
The recently released FileMaker Pro v14 is the first version of FileMaker Pro that can be installed and run as either a 32-bit application or a 64-bit application – on Windows you have to choose which version to install, and on OS X FileMaker Pro is installed as a single application bundle containing both 64- and 32-bit versions (you can choose which version to run via the Get Info window).
When using the 64-bit FileMaker Pro application you will need to ensure that any plug-ins you install are the 64-bit versions – 32-bit plug-ins won’t load with the 64-bit FileMaker Pro application. The same applies to the 32-bit FileMaker Pro application – it will only load 32-bit plug-ins.
How do you check which version of FileMaker Pro v14 is installed in order to install the appropriate version of the plug-in? FileMaker have added a new function to v14 for just this purpose – Get ( ApplicationArchitecture ). This function will return the following depending on the platform:
i386 for the 32-bit version of FileMaker Pro
x86_64 for the 64-bit version of FileMaker Pro, FileMaker Server, FileMaker WebDirect, and Custom Web Publishing
arm7 for FileMaker Go running on an ARMv7-based device
arm7s for FileMaker Go running on an ARMv7s-based device
arm64 for FileMaker Go running on a 64-bit ARM-based device
Things to consider: There are Mac and Windows versions, for 32 bit and 64 bit, for desktop clients and servers. FileMaker go does not support plugins.
Since you are able to store plugins in container fields, it’s possible to write a script to test for platform type and install a plugin on startup if not present already. Much easier for rolling out and maintaining your client computers as time goes on. Read it all at the link.