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.
Tag Archives: FileMaker
FileMaker: Getting Live Exchange Rates
This technique uses Applescript and cUrl to get the current exchange rate between two currencies. The results are returned to a field within FileMaker.
For this we’re using a database called PRODUCTS and a temporary global field called Temp 001, so change these accordingly for your database.
FileMaker: Detecting web viewer image load
In FileMaker you can load content in web viewer boxes. While useful, they load at a different pace than the rest of the record they are in. For detecting the load of an image in a web viewer I use the following code.
FileMaker: Code 128 barcodes, the free and easy way
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.
FIleMaker: Fixing The Annoying Error 101
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.
What can we do?
We we have two choices: ignore the benign error or use another method. I chose the latter, a method that won’t trigger the error.
Information To Share 