You may have already seen my hardware integration demo where I combined iPads, iPhones, motors, barcodes, RFID, digital scale, mobile receipt printer, and payment cards. Although everyone loved the automated moving parts built from LEGO, the after-session questions and discussions were actually mostly focused on RFID and NFC.
We can build native iOS apps with the FileMaker platform but we struggled doing that too often. Xgode has changed this for us, and now it is not an exception when we build a FileMaker based native app more than five times on the same day. Why is the life after Xgode so different from the life before it?
Since the introduction of WebViewer, Google Maps were quite popular in FileMaker solutions. What many FileMaker developers may have missed though is that in most cases they were using Google Maps API illegally and Google could ban their API key or IP address from accessing the feature at any time.
The idea of being able to off-load time consuming tasks from FileMaker Pro to FileMaker Server is as old as the scripting abilities of FileMaker Pro, which were introduced with the FileMaker Pro 3 release. But it was the FileMaker Server 13 that finally made this idea easy to implement.
One of the questions I am getting from time to time since I testing FileMaker performance is whether there is any significant difference between performance of text and number fields, So I tested it and discovered that there is even a case when indexed field can be slower than an undindexed one.
In May, I participated in Pause[x]Berlin 2013, a European format of the popular unconference Pause On Error, organized for FileMaker developers by FileMaker developers.. There I presented a session called Optimization Madness focused on optimizing performance of FileMaker solutions.
A lot has been written and said since FileMaker 12 was released about its speed, compared to FileMaker 11. Emotions left aside, if I was supposed to compile all the recent findings into a single brief message, I would say that some people find FileMaker 12 slower than FileMaker 11 while others experience improved performance.
This example demonstrates that even a single-step script can be optimized. You just have to think a little bit out of the box... I was showing this as a surprise in my session Marvelous Optimizations at Pause On Error [x] London 2011. I used a sample file with 25 fields and 5,000 records and imported these records 5 times in a row in just 13s.
The second example I was showing in my session Marvelous Optimizations at Pause On Error [x] London 2011 was the script for selecting Random Set of Records. I found this example in the FileMaker Knowledge Base and optimized it to run at least 158 times faster when selecting 10 random records out of 50,000.
This is a fresh story of me spending hours trying to fix a technical issue and accidentally revealing a gold nugget. A few days ago one of my nightly server-side scripts stopped working without any apparent reason. But when I tried to run the script in FileMaker Pro it worked just fine. I really needed a way to debug the script on the server.
I noticed that one of the articles updated in the official FileMaker Knowledge Base on September 23, 2011 was explaining how to select a random set of records in a FileMaker database. I was wondering how fast the currently recommended technique is and whether I can make it faster with the help of FM Bench.
Just today I needed to decode HTML encoded text in FileMaker. After checking few functions I found one that seemed pretty good. Written in 2009 by Fabrice Nordman and named HTMLencoded2Text, this custom function was converting my imported text OK at first sight.
I have just read Anders Monsen's post "Read on Mightydata's blog" A Simple Debug Function for PHP at the "Open the Mightydata's blog" Mightydata's blog. My first thought was this is similar to what I have been doing since I learned PHP a few years ago.
Last week Hal Gumbert mentioned on Twitter that he was “working on a FileMaker quote to display and edit a BOM ( Build of Materials ) that can go 9 levels deep.” Probably the most efficient and user friendly way to implement this is using a tree view with collapsible/expandable items.
Yesterday I got so stuck with an issue that I wanted to send a question to a mailing list. But (un)fortunately I sent it from a wrong e-mail address so it did not reach the list. Then, before discovering that I used the wrong e-mail address I actually resolved the issue, so now I can share this for the case it can help someone.