A few years ago, I worked on a FileMaker project where the client told us that every week they need to import about 7,000 rows of data that represent some information that this company uses. And every week there might be some modified records, some records that don’t show up any longer, and some new records that hadn’t already existed. For this example, let’s just call it this data “Products”.
Now more than ever we’re relying on Perform Script on Server (PSoS) to maximize FileMaker performance, so naturally a need arose for a way to proactively monitor how many concurrent scripts are being triggered. This type of logging helps us see if we’re reaching our maximum limit, or have a rogue script eating up processing power.
InspectorPro 5.5 is here! With it come some great enhancements and complete support for FileMaker 14:
As a FileMaker developer you probably spend a big chunk of your time writing scripts. The new Script Workspace in FileMaker 14 is going to help you in a big way. It’s a breath of fresh air and at first glance it might seem trivial in that we now have colors and we actually can have white space, but there are many other productivity improvements that lurk beneath the surface.
FileMaker 14 is here, and while the Database Design Report (DDR) hasn’t changed, here’s a “Getting Started’ walkthrough for using InspectorPro with the latest version of FileMaker Pro Advanced.
For the longest time I thought field labels were something special and there was some sort of connection between the label and the field. So if you have ever created a new field and put that field on the layout with the label to the left of it. Then 10 seconds later you change your mind and decide to rename the field. Presto your label has also been renamed.
When you delete a field that calculations or scripts depend on, FileMaker provides great warnings.
I recently moved to OS X Yosemite, and once again repeated the annual cycle of wondering whether or not my existing solutions will be compatible with the new version. I’ve loved using AppleScript to trigger OS X Notifications from FileMaker since they were introduced in OS X Mavericks, but they stopped working as soon as I installed Yosemite.
To describe this next technique I came up with my own acronym, and I call it "NoSSR", which stands for Not Only Sub-Summary Reports. The goal of this blog post is to show you a way to build and deliver similar results but in a statically defined way. Another way to put it is to architect for performance, so let’s see what can be possible. This post also assumes you know how to build a FileMaker sub-summary report layout already.
Continue reading “NoSSR ( Not Only Sub-Summary Reports )”