Your Interests

  • Services
  • Products
  • Case studies
  • Goals
  • Functional areas
  • Events
  • tech

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

An Interest was added! Interests were added!

was were added to Your Interests Panel.

Within our site, when you click a that item is added as an Interest.

You can open "Your Interests Panel" with Open Side Panel Created with Sketch. below. Also, from the gray panel on the right (“Your Interests Panel”) you can select interests from drop-down lists, among several categories.

All interests you select can be submitted together on our contact form. This lets us know these are topics you’d like to discuss with us.

Exciting...





Requirements

  • macOS 10.13 – 10.15, 11.0, and Linux using CentOS 7.8
  • FileMaker Client versions 17 – 19.1
  • FileMaker Server versions 17 – 19.1 (including PSoS, script schedules, CWP, WebDirect)

If using earlier versions of FileMaker or macOS, version bBox 0.85 may still be downloaded. Starting with version 0.90, bBox is 64-bit only. Linux support was added in version 0.97.

 

Plug-in Installation (Client)

The demo file will install the plug-in if needed on both client and server (plug-in installation must be enabled on server).

You can install manually for an individual user by starting at their home directory, and putting it in:

Library/Application Support/FileMaker/FileMaker Pro/{version number}

There is a debug version of the plug-in in the DEBUG folder, which may be helpful for debugging some issues. It will send extra output to the system log, which you can view using the Console application in /Applications/Utilities or the log command in Terminal.

Plug-in Installation (Server)

bBox is fully server-side compliant, although running server-side does put limitations on some functions (esp. AppleScript) that typically work with a logged in user. For details on installing a server-side plug-in:

 

Install Plug-In File Script Step (Client & Server)

To use with either a client or server side script, simply drag the bBox plug-in file into a container field, and then add the Install Plug-In File script step to your system’s initialization script.

You should first check for a previous install so that you aren’t needlessly re-installing the plug-in each time. Testing for a result of “?” from the bBox_Version function would be a good start.

Also, when using this script step server-side, the last installed version is the version used by all scripts run on that system, so you may need to be more careful about version dependency issues on systems utilizing server-side scripts.

With FMS for Linux 19.1, the Install Plug-In script step may not work as expected. Instead, copy the .fmx version of the plug-in to:

/opt/FileMaker/FileMaker Server/Database Server/Extensions/

Then ensure FMS has file access:

sudo chmod -R fmserver:fmsadmin '/opt/FileMaker/FileMaker\ Server/Database\ Server/Extensions/bBox.fmx'

 

Demo File Installation

The FileMaker demo file can’t be run from a read-only location (e.g., a disk image), so before using it you’ll need to copy the demo file to somewhere like your Desktop where you have write access. It can also be hosted on FileMaker Server.

The demo file will install (and possibly update) the installed version of the bBox plug-in.

We use cookies to give you the best experience possible on our site. Learn More