Learning Claris FileMaker

Working remotely this past year has meant mostly accessing FileMaker systems over a WAN.

This has posed immediate challenges to systems that were not originally designed with that in mind.

So…let's talk about Transactions: understanding what they are, how they relate to CRUD operations and database normalization, and how you might use transactional concepts to improve FileMaker performance, especially over a WAN.

If you are struggling with solution performance, we’ll look at a way to build a baseline so you can have a starting point as to what you can strive for in terms of solution performance.
...

The transactional method of working with records has one goal: to ensure all changes to records (additions, changes, or deletions) are done at once or not at all.

We’ve talked about this before.

The transactional method prevents some records in a discrete set (such as invoices and invoice line items) from being changed while others are left in a previous state.

We’ve reviewed in the past how to create records in a transactional method (here and here).

Now let’s turn our attention to the FileMaker transactions and editing records.

Review the Concepts
There are a few important points about the transactional process.

If we keep these ideas in mind, we will design a workflow that works for FileMaker transactions editing and continues the trend of data confidence. 

Read more about transactions on the blog ...