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.
As time passes by, we quickly and easily get used to new technologies and new versions of all the apps we use. Occasionally, the history decently knocks on the door, checking if we remember. Just like recently, when a customer contacted us, asking for help with converting his invoicing solution, made in FileMaker Pro 1.0, to the current version.
Many years ago, when designing backup strategy for our server, we decided to take advantage of one typical aspect of FileMaker databases. By using a simple bash script, we could easily keep a history of 4 times more backups than without compression...
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.
Experts in optimization and hardware integration, platinum member of the FileMaker Business Alliance. We build custom apps, FileMaker plug-ins, native apps for Mac, Windows, Linux, iOS, and Android, we are able to to integrate even hardware and software noone has integrated before.
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.
This is the first example I was showing in my session Marvelous Optimizations at Pause On Error [x] London 2011. I already wrote about this optimization some time ago. It’s the one that led me to unveil the Marvelous Optimization Formula. I took the example and added FM Bench Detective into it to be able to exactly measure and examine what happens.
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.
Sometimes, not often, I accidentally achieve results that look too marvelous to be real. But they are. Just like in this case. Last week I assigned Petr, our internal system developer, the task to optimize one server-side script. The script recently started taking over 8 hours to run and reaching the expiration limit we have set for it.
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.
Last September I wrote an article about a custom function that I optimized to evaluate hundreds times faster. At the end of the article, I challenged my readers and myself by claiming that the already optimized custom function can be optimized even further. Do you remember? Later on I actually really optimized it again, and talked about this.