I use the Plastic plug-in from 360Works to do credit card processing within FileMaker. It’s a daunting task at first, but once it is setup, it’s absolutely great. This guide explains how to setup a First Data credit card gateway API for use with FileMaker using the Plastic 2 plug-in.
Getting live data from outside sources is often a requirement of FileMaker solutions. In this post I’ll explain how we can do a simple import of JSON data from a URL. I updated this post to include two solutions, one using AppleScript and the other utilizing a new (easy) function in the latest editions of FileMaker to do most of the work.
I wasn’t willing to pay $49, $99, or $199 to add barcodes to my databases. Luckily, we don’t have to pay for something that we can do ourselves for free!
The first step will be to insert a custom function the converts ASCII text into Code 128, which requires both a check sum and character conversion. I have supplied the necessary code at the bottom of this post, and even though it’s not my code, it’s quite awesome. Just save it as a custom function in your database with the name “cfCode128” and with inputs “pString” and “pCodeSet”.
So once you have the function setup, use it to convert data in a field and apply a Code 128 font, like this one.
When creating loops that traverse through all the records of a found set, most all of us use the useful “Go to Record/Request/Page [Next; Exit after last]” function. It’s quite nice, since it prevents a loop from continuing into infinity when you reach the last record of a found set. However, you will always get an Error 101 from this.
Error 101 is telling us that the record we want is not found. For this case, the record we want is the next record, which doesn’t exist because we’re already at the end. You would think the built in function would suppress this error when you select to option to exit after the last record, but the error still gets logged, and will pop-up if we use the debugger window or if we are running a server script. Continue reading FIleMaker: Fixing The Annoying Error 101
When editing a live FileMaker database, we’ll sometimes need to force clients to commit their records before the update can happen. If our users are on remote machines, this can be a real problem. The general fallback approach is to send a disconnect request from the FileMaker Server. This will close the database the client is using, so it isn’t the most friendly method.
Filemaker’s date field is not very kind to users…
…especially ones that like to type instead of using their mouse to select a date. However, we can fix this to make a more pleasing user experience. Continue reading FileMaker: More Useful Date Fields