Our team of experience developers has just helped our client to safely migrate database from FileMaker 10 to FileMaker 18. Let us take care of your solution. New FileMaker version is just the beginning.
You know what it feels like to be the hero who has just fixed “the thing”. Imagine you have spent hundreds or thousands of hours developing your solution, and now you’re ready to deploy it. Is your work done? The truth is that until now you have been playing your favorite game. Now the real life begins.
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.
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.
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.
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.