When you’ve been using FIleMaker as long as I have, you know we’ve done all kinds of crazy things to get image masks to work on our buttons. Here’s how I went about implementing Button Image Masks in FileMaker 13.

As part of a shell script I’m cooking up, one of the required tasks is to list all currently hosted database files on a Mac OS based FileMaker server. This may get deployed over multiple servers, and I want to keep it as simple and trouble free as possible.

It's FileMaker Developer Conference 2014 this week, with 8 Beez in San Antonio for DevCon. We're studying new development techniques from FileMaker Inc. and our industry peers, sharing a few methods of our own and even riding a few mechanical bulls at a real live cattle ranch! Several members of Beezwax’s development team are featured presenters, and several more are hosting and facilitating Unconference Workshop sessions.

Introduction I hope that since our previous blog post you have been exploring the possibilities created by FileMaker’s Perform Script on Server (PSoS). This article is a continuation of the PSoS discussion and includes more cool things you can do with it, specifically running database imports on FileMaker Server.

Beezwax was a sponsor and participant in the first ever d3.unconf in San Francisco this weekend. This “Unconference” event was created as a one-day gathering of data visualization practitioners, centered on d3.js, a powerful and flexible JavaScript data visualization library. Here’s info about the conference, examples of how we use d3 at Beezwax, and pointers to learning more about d3.js.

Working with older Java applets with Java 7 Update 51.

Enable client statistics logging to better monitor a system’s usage.

Use FileMaker 13’s popover object to create more user-friendly pop-up menus

Sometimes a FileMaker user wants to stop things, right in the middle of a process! Little do they know that a time-consuming script has only looped over 10 percent of the records, or set flags in half of them, etc. What to do now? Well, what if there were a simple way to allow the user to cancel the script even in the middle of performing its task, then have another script take over and clean up as if nothing ever happened? If that is what you need then you are in the right place.

At its core, InspectorPro v4 is a FileMaker database. The previous version, Inspector Pro v3 was originally architected as FileMaker Pro 7 file, and continuously remodeled as we moved all the way through FileMaker Pro 11. InspectorPro 4 on the other hand was rebuilt from the ground up as a FileMaker 12 solution. I wanted to tell you more about the approach I used, including extensive use of the new ExecuteSQL feature. Hopefully it will give you some ideas as you start to re-think, and ultimately rebuild, solutions in FileMaker 12.

In this post, we'll learn two lightweight techniques that give full control of button appearance and behavior: the <em>conditional overlay</em> and the <em>conditional clear</em>. These techniques provide the methods needed to successfully resolve the conflict between 'interactive formatting' and 'semantic misinformation' posed in our previous <a href="http://buzz.beezwax.net/2012/12/15/button-up">Button. Up.</a> blog post.