Introduction to the series.
Given a FileMaker production setup, such as a given server box and settings, concurrent user count and network connections, what can one do to improve the speed of the database? That is, how can one refactor it: redesign and reprogram to improve speed while keeping the functionality exactly as it is? There are many ways, but before getting into nitty-gritty topics, this post and the series it belongs to, will deal with low-hanging fruit. They give an overview of all the easy tips and tricks that I came across during the past ten years or so.
This post lists all the low hanging fruit. The first three are the most important and easy tips. The last of the three is about working with layouts and so are the following ones. Next follow tips regarding scripting and calculations. The last one is about an overall UX design trick.
Click an item to see its post. If there is no link, the post is not yet written.
- Store if you can
- Perform data intensive scripts on the server
- Use styles for layouts
- Freeze the window and use empty layouts for long running scripts
- Go to Find mode before changing the layout
- Insert instead of set a variable
- Choose Choose ( ) instead of Case ( ) in case you can
- Test for the most likely condition first
- Use Let ( ) for setting many variables
- Limit the use of ExecuteSQL
- Distribute wait times for the user
Rubber Boots Data 