FileMaker Tip-n-Trick - Caching for Speed

[eXcelisys]

Dogged by a Slow FileMaker Database?

Cache in on this Quick Tip to Improve Layout Load Times & Report Generation

By Joe Cellino, FileMaker Developer

 

Have you ever wondered, “What is taking this report so long to generate?” or “Why does this layout take so long to load?” It may be that your FileMaker fields are set up inefficiently. If you have unstored calculation or summary fields on your layout, this will most certainly be the issue. Just as the names indicate, “unstored” calculation fields and “summary” fields don’t store any data. They must calculate the data each time the field is displayed. It may be easier to use unstored calculations in order to get your database functionality working, but this will inhibit your system from scaling with your business in the long run. The good news is — you can improve FileMaker performance with this data caching trick. Read More - > https://excelisys.com/dogged-by-a-slow-filemaker-database-check-out-this-data-caching-tip/

[comment]

 

[eXcelisys]

1 hour ago, comment said:

 

Your first comment is valid and this was included as a demonstration of what NOT to do as a developer. We've seen several cases where "citizen developers" have made that mistake.

Your second comment is not entirely true since we can just prevent access to the field in Browse mode so the user won't be able to edit the value. This allows number fields with auto-enter values to behave the same as a stored calculation that returns a number.

[comment]

1 minute ago, eXcelisys said:

we can just prevent access to the field in Browse mode

Sure, you can always make it complicated instead of making it simple. 

 

2 minutes ago, eXcelisys said:

This allows number fields with auto-enter values to behave the same as a stored calculation

But the behavior is NOT the same: for example, the value in a calculation field can be copied by the user. If you have disabled entry in  Browse mode, then it cannot be copied. 

 

[eXcelisys]

57 minutes ago, comment said:

Sure, you can always make it complicated instead of making it simple. 

 

But the behavior is NOT the same: for example, the value in a calculation field can be copied by the user. If you have disabled entry in  Browse mode, then it cannot be copied. 

 

We agree that FileMaker provides us with options.

[comment]

I certainly do not agree with such bland statement. The options are never the same; it is up to the developer to carefully weigh the pros and cons of each and select the one that fits best the task at hand. 

[eXcelisys]

1 hour ago, comment said:

I certainly do not agree with such bland statement. The options are never the same; it is up to the developer to carefully weigh the pros and cons of each and select the one that fits best the task at hand. 

eXactly - options. Which option works best for each particular use and situation and skill set.

[Dr.Gopala krishnam raju AMBATI]

On 10/23/2019 at 8:53 PM, comment said:

Sure, you can always make it complicated instead of making it simple. 

happens each and every-time when we enter layout mode

i am facing same problem of summarising every-time i add new record and committing entire patients record data is summarising the calculations and i had to wait which i am feeling awkward will try this new method

[LaRetta]

On 10/23/2019 at 8:16 AM, eXcelisys said:

... we can just prevent access to the field in Browse mode so the user won't be able to edit the value. This allows number fields with auto-enter values to behave the same as a stored calculation that returns a number.

The problem with using layout-level restrictions on values which must be correct, is that forgetting and placing the field once on a layout with entry to field left ON, and inconsistent data will result.  A stored calculation provides safety from this accidental field placement and as Michael says, can be copied because the field can be entered.  It'll also allow scrolling.