We wanted to give everyone an update on the compatibility status of our products with Mac OS X 10.6 Snow Leopard:

Initial testing with the latest versions of our plug-ins (DoSQL, DoScript, PrinterSwitch), have not shown any compatibility issues with FileMaker 10 on Snow Leopard.

We expect AutoSender 2.5.5 to work fine with FileMaker Server 10, once the 10.0v2 upgrade is made available by FileMaker.

The latest version of Clip Manager (3.1.3) has been tested and works fine.

There are some issues with our FileMaker to vCal XSLT and time zones in Snow Leopard. We hope to address this in an update in the next couple of weeks.

If you do encounter any issues with one of our products on Mac OS X Snow Leopard, please let us know at http://myfmbutler.com/support

Today I implemented some script triggers in an existing project and something strange happened. My navigation scripts that have worked correctly for years, suddenly stopped working. I checked my scripts over and over again and couldn't find any clue, until I discovered an unexpected behavior.
(more...)

Conditional formatting is a great tool to enhance your layouts and add additional functionality to your solutions, e.g. for calendaring. But sometimes conditional formatting can slow down the display of your layouts, because FileMaker has to calculate all the conditions you have defined. Today we are going to look at a technique that allows you to speed up your calculations by caching some results temporarily.

(more...)

We just released version 1.7.1 of our PrinterSwitch plug-in.
PrinterSwitch is a FileMaker Pro 9 (and 7/8/8.5) plug-in for Windows and Macintosh that allows you to easily control printer switching from within your FileMaker solutions.
This new version fixes the PrSw print-to-PDF functionality on MacOS X Leopard.

A couple of weeks ago, we talked about the “Beam me up, Scotty” or “tele-porting” method. This technique described how you can transfer found sets from one table occurrence to another.

This week's technique will show you how you can write a re-usable script to go to a certain record or found set, independent of the current context.

We call this technique the “hub” method. It is also described in the myFMbutler/SHpartners Development Guidelines.
(more...)

If you haven't upgraded to FileMaker Server 9.0v3 yet, and are an AutoSender user, we strongly advise you to upgrade asap.

FileMaker Server 9.0v2 contains a bug where database sessions can't be closed properly (including disconnects) while an ODBC or JDBC session is active.

If you are using JDBC with AutoSender to connect to your mail sources, you may experience this problem.

As a workaround on 9.0v2, stop the AutoSender service/daemon first, before closing the files. Or upgrade to 9.0v3 to solve the problem altogether.

Have you ever wanted to automatically send birthday greetings to your important friends and customers?

In today's example, we'll take a closer look at how we can combine the power of FileMaker Server 9 script scheduling with AutoSender for automatically sending mail messages from FileMaker Server at scheduled intervals.

(more...)

AutoSender 2 has been released last week. We would like to thank all our beta testers for the invaluable feedback we received !

Existing users of AutoSender 1.x can upgrade to 2.0 for EUR 49,- or about USD 70,-. All AutoSender purchases after October 1st, 2007 are entitled to a free of charge upgrade.

More details are available on the AutoSender product page.

At the last "Clarify Confituur" session (a Dutch-speaking FileMaker User Group), someone asked a question about how you can restore a found set, if you lose your found set during a script.
In this article we will show you with a simple technique that demonstrates how to do this.

(more...)

We just updated our FileMaker to vCal XSLT to version 1.2. The free FileMaker to vCal XSLT solution allows you to subscribe to FileMaker calendar data from vCal-compatible calendaring programs.
With this version, iCal should now update calendar events properly under Mac OS X Leopard. In this version, we changed the DTSTAMP parameter in the XSLT to use the modification date instead of the creation date of an event.

Check this article or more information on how to use this solution.
Download version 1.2 here.