FileMaker Memory Bug?
For all my time with FileMaker, there's this peculiar aspect of one's learning journey where small bits and pieces of information come to you in odd ways. You either happen to stumble upon them, or you're told about them through the grapevine. Not from the company itself.
While most large companies are often busy with the business of improving their software, their outbound communications about certain things aren't always prompt or highly detailed. Personally, I love what Claris has been doing with FileMaker communication in the last few years. It's a night and day situation compared to just 5 years ago. There are, however, situations where you have to hear about a particular feature from a close parter like Soliant. Even Claris themselves didn't publicize the fact that FileMaker Server 19.5 supported Perform Script on Server - running on Server - via a flag named SupportNestedPSOS. Go ahead, search for it in Google. You won't find it anywhere on any of the Claris sites (at least as of the posting this article).
Which brings me to technical issues and possible bugs. Unless you frequent the Claris Community forums, it's unlikely you've heard about the 9 year issue of FileMaker being a total hog when it comes to memory allocation for certain functions. All credit goes to Alex Zueiv for this long running discovery. At this stage, it may be known and intentional by Claris, but it certainly is an eye opener. So much so that I decided to make this video to increase awareness. Like you, I like my software to run as efficiently as possible and workarounds, hacks, what have you, I'm going to take advantage of the findings because with software, that's just what you do. You optimized until it's as good as it can be!
Click the title or link to this article to view the video.
There are no comments to display.