Add Simple Logging to your FileMaker Application

  • 4

Add Simple Logging to your FileMaker Application

Tags : presents Matt Navarre discussing App.Works’ new free downloadable module fmLog.

Tuesday, September 27th | 2:00 pm ET | Register Now! 

Who is using your database, and for how long? Which layouts and scripts are being used, and which aren’t? How do you know when a record was deleted or modified?

When we start working with new customers on an existing database, they almost never have a logging system in place. Why is this? Most likely it’s because logging is perceived as complex, slow and unnecessary. But it doesn’t have to be.

Join FM Academy and Matt Navarre, Founder of AppWorks, as we break down the mystery of logging and demonstrate how you can use fmLog to add a simple, yet effective system to your existing FileMaker applications.

During this webinar we’ll discuss:

  • Why you should have a logging system in place
  • Tracking Who / Where / Why / When / How
  • The many features of fmLog and why it’s the right tool for the job
  • How to integrate fmLog into your existing system in just minutes

Who should attend this webinar?

  • FileMaker Developers and Users
  • FileMaker Administrators

About the Sponsor:

This webinar is offered by the FM Academy, a consortium of leading FileMaker development companies in the United States. All FM Academy members are platinum-level members of the FileMaker Business Alliance, and our purpose is to further educate FileMaker users and developers to encourage best practices and foster further adoption of the software.

Adding Simple Logging to your FileMaker Application
Date: Tuesday, September, 27, 2016
Time: 2:oo – 3:oo pm ET / 1 pm CT /  11 am PT

After registering you will receive a confirmation email containing information about joining the Webinar.

Space is limited.

Click here to reserve your Webinar seat now.

Past Webinars:

Click here to view past FMAcademy Webinars


If you missed it, here’s a video of Matt’s webinar:




September 27, 2016at 8:24 pm

Where can we download the recorded Webinar, it would be great to have it, it was really interesting

Joshua Willing Halpern

November 20, 2016at 10:24 pm

Hey this doesn’t look transactional. What happens if a record is reverted? Is there a ghost log line left over?

    David Weiner

    November 21, 2016at 9:49 am

    The transactional nature of the logging depends on how you implement it. You can put the logging script wherever you want. If you were to add the logging step to an OnRecordCommit trigger, and include some logic to prevent committing (for example by using an Exit Script [False] step), you would effectively keep a log from being created, and thus have no “ghost” log line. You could also use the fmLog script to log the record revert itself. If really just depends on where you put it.

Leave a Reply

4 × four =