This is part 3 of a video series on FileMaker Transactions.  It might be helpful to watch part 1 andpart 2 first. But it’s not required. In this video we took a look at why transactions are important to syncing FileMaker and FileMaker Go. We use GoZync, our fully transactional sync framework, to demonstrate why transactions are so important to sync.

https://www.geistinteractive.com/2014/03/21/syncing-filemaker-transactions/

This video is part 2 of a series on FileMaker Transactions. Part 1, titled “Fixing Slow FileMaker Reports” demonstrated one of the many reasons why transactions are an important part of building multi-user FileMaker apps.  In this video, we break down the simple FileMaker Transaction that we briefly see in part 1.  The video continues with a brief introduction to the low level FileMaker features that are used to build transactions safe scripts.

https://www.geistinteractive.com/2014/03/11/simple-filemaker-transactions-video/

Fixing Slow FileMaker Reports

This video is part 1 in a series on FileMaker Transactions and why you should use them. In this video, we look at a slow FileMaker Report. The report is slow because it is based on unstored calculations. We look at a way to speed up the report, by storing data closer to where the calculation needs to occur.  This lets us create our report using less unstored calculations. The result is a report that is much faster.

However, this opens our solution up to database integrity problems because no we have the same data stored in many places. In theory this is a bad practice. But in the real world of multi-user FileMaker applications running over the internet, it turns out to be something you will need to do.

We solve this problem by employing FileMaker Transactions to make sure that we can reliably keep the de-normalized data in sync.

https://www.geistinteractive.com/2014/03/10/fixing-slow-filemaker-reports/

ModularFileMaker.org has done really well in 2013.  There are lots of modules available now, and the list keeps growing. One question that we are trying to answer is how do we organize our “Modules” into an “Application?  This is a topic that will likely remain beyond the scope of the Modular FileMaker spec, as it is almost antithetical to the whole approach.  Modular FileMaker specifically stays out of the Application Framework conversation. But in my own projects an organizational pattern is starting to emerge. I thought I would share it.

 

Start With the End in Mind

What I was looking for was a way to work… http://www.geistinteractive.com/2013/12/26/modular-filemaker-app-development/