The techniques of this post are limiting the use of ExecuteSQL and how to reduce wait times for a user when all else fails. … More Accelerate by refactoring. Low hanging fruit 6.

In this post: one tip which applies to all programming, but has a maintenance trap, and one very straightforward performance tip regarding setting variables. … More Accelerate by refactoring. Low hanging fruit 5.

This post addresses two easy scripting and calculation improvements .   6 Insert instead of set a variable One way to collect data from high number of records ( or websites or other sources ) is to visit them one by one and store the collected data in one variable. Suppose that one wants to … More Accelerate by refactoring. Low hanging fruit 4.

This post will deal with a couple of ways to prevent FileMaker from unnecessarily generating a layout and performing the necessary calculations while running a script.   4 Freeze the window and use empty layouts for long running scripts Perhaps the most basic means that exist to prevent FileMaker from unnecessarily generate a layout and … More Accelerate by refactoring. Low hanging fruit 3.

This post will deal with two very well know speed improvements: performing scripts on the server, and using styles for layouts.   2 Perform data intensive scripts on the server If your application is running on a server and users work with FileMaker client applications on their computer or iOS device, it makes sense to … More Accelerate by refactoring. Low hanging fruit 2.

 This post is fully dedicated to the most important tip. 1 Avoid calculation on the fly. Store if you can. This is perhaps the most iterated one on the internet and still worthy of being mentioned first. Calculations are performed on the fly, and fortunately only performed when needed. However, within FileMaker they occur in … More Accelerate by refactoring. Low hanging fruit 1. Store if you can.