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 the benefit of knowing what your solutions' users and scripts are doing, it's highly suggested you take advantage of this wonderful logging system.įor 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. One of the biggest benefits of using a server-based logging system is that you can more easily troubleshoot those harder Perform Script on Server processes. You'll also find some creative solutions to replicating the exact user environment from when an error occurred for a client. Like the previous versions, this solution has both error handling and logging included. There are certainly some similar aspects, but we've got some new features and functionality added in. If you've not watched the previous video from 2020, then you'll find a link to that one below. We're always trying to take advantage of newer features and improve what we use in our solutions. The functionality we had in 20 is different than what we have now.

With the release of this video and technique file, you'll find an updated version of a long-running topic which goes back to 2013. If you haven't added logging into your FileMaker solutions, then you don't know what you're missing, and there's no better time than the present to do so.

Filemaker pro 16 tutorial