So let’s say you spent a couple of hours on making a great FileMaker script or layout. You are testing it, making some additional changes and at a certain moment your script is broken. You get a little panic attack. What did I change? Do I have a backup?
If you’re using Clip History, you know exactly what you can do.
In this post, we will explore the Clip History and give you some insights on why we implemented it in Clip Manager.

Read the rest of this entry »

Last week I had an interesting discussion with Kevin Frank.
We were trying to figure out what would be the best way to insert or update dates when using the myFMbutler DoSQL plug-in.

Read the rest of this entry »

In our previous blog post, we showed you how you can share your clips via a shared folder on your local network. But maybe you want to share your clips with your fellow FileMaker buddies over the Internet. Shared folders can be an option but it requires that you are online all the time and can rely on a fast network. In the next couple of articles we will explore several alternative ways of sharing your clips.
Read the rest of this entry »

Sometimes you want to share your Clip Manager clips with your colleagues. In the next couple of weeks we will explore several ways to do this.

If you are on a local network the most obvious way to share clips is via a shared folder on your network.
Read the rest of this entry »

During FileMaker Devcon in San Francisco we received a lot of positive feedback for Clip Manager and we wish to thank all of you who were there for their valuable input. Many among you are using Clip Manager for copy-and-pasting of Custom Functions into FileMaker. Some of you admitted they would love to use Clip Manager more, but didn’t figured out yet how to get started with this.
That's why we decided to launch a new series of posts called 'Clip Manager 101'. These posts are aimed squarely at those who are new to the Clip Manager. We’ll also be sharing some tips and trick for people already familiar with Clip Manager.

If you have any suggestions, questions or a fabulous trick that you would like to share, leave us a note at info@myfmbutler.com.
Read the rest of this entry »

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

We just released an upgrade to our Clip Manager for Mac OS X.

What's new in version 3.1.3 Mac?

Bug fixes

How to upgrade ?

1° Use the built-in updater to automatically install the latest version
2° If you are using the new demo installer, some people have reported issues when upgrading. In order to avoid any problems, please remove your current app from /Applications/myFMbutler Clip Manager/ before installing the upgrade.

The Japanese verison will be available soon, exclusively through fmgateway.jp

If you are attending DevCon, myFMbutler will again have a booth at this year's conference. You may want to drop by the booth to get a sneak peek at a future version of Clip Manager, that is currently under development.

Also, during DevCon, myFMbutler products will be offered at a 25% discount when customers use the coupon code 'DEVCON09' in the myFMbutler web store.

Last week we released Clip Manager 3.1.2 for Mac, now the Wndows version has also been updated.

This is a bug fix release:

Several smaller bug fixes

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.
Read the rest of this entry »

For this week's blog article, we want to extend a special thanks to Kevin Frank and Dave Walton who sent us the example.

When using DoSQL to create a ChangeLog of your records, you want to avoid creating log records when nothing has actually changed.

The trick is to prevent DoSQL from firing unless you want to log a change... take a look at the example and check the validation on _K in the Data table... basically, if the parent sees that nothing has changed since the last corresponding ChangeLog record was created, then doSQL won't trigger.

Note that if you have no ChangeLog record for a given parent record, then it will be created *regardless* of which parent field you edit, but... once you have at least one change log record for a given parent, then any "don't log" fields will be respected.

The thing I like about this technique is that ChangeLog records will be created when a Replace is performed and when parent records are imported.

DoSQL ChangeLog Example

DoSQL Plug-in download