This is a quick tip about how PSOS can vastly improve performance of the ExecuteSQL script step. Recently we received feedback on one of our solutions that uses Execute SQL to build a virtual list used in a picker window. The feedback had to do with the slow performance of loading the picker window. The user complained of the window sometimes taking up to 30 minutes to load. Obviously this design was not ideal!
“97% of the time, Premature optimization is the root of all evil”
I think I first read this quote of Tony Hoare in McConnell's “Code Complete” and have thought about it many times when doing code reviews, during my own programming, and when talking with others about programming problems they’re trying to solve.
With the release of FileMaker 16, we have seen a great number of new and improved script steps. FileMaker 16 extended the capability of the Save as PDF script step, now allowing it to work partially with WebDirect, FileMaker Go, and Server, however there are a few things of note.
I have been fascinated with impossible places. Things like the Doctor Who Tardis, Hypercubes, and M.C. Escher’s impossible objects, lead me to happy daydreams. Lately I have been wondering, would it be possible to create some of these physically impossible spaces. Could I create them in Virtual Reality (VR), and if so, what would they feel like?
Have you ever needed a user to quickly pop into their FileMaker solution and not become disconnected when switching networks or putting the device to sleep? This is a common request for FileMaker Go users, but can also be useful for desktop users who keep their solution open all day. There are a couple different ways to make this work, but as I found out recently, there are also some things to keep in mind when you are troubleshooting.
Alanna investigates word cloud generators.
