At this stage, it may be known and intentional by Claris, but it certainly is an eye opener. All credit goes to Alex Zueiv for this long running discovery. 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. Which brings me to technical issues and possible bugs. You won't find it anywhere on any of the Claris sites (at least as of the posting this article). 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. There are, however, situations where you have to hear about a particular feature from a close parter like Soliant. It's a night and day situation compared to just 5 years ago. Personally, I love what Claris has been doing with FileMaker communication in the last few years. 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. You either happen to stumble upon them, or you're told about them through the grapevine. 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.

Filemaker pro tutorial 13