This is why sometimes a script goes through several “iterations” even if the basic functionality is working. It involves speed and resource(s) the script uses. Efficiency is hard to measure, easier to spot in a script.Finally, there should be no unplanned “side-effects” of the script: make sure there are no unwanted changes or unintentional behaviour resulting from running the script(s). If the answer is yes, start the scripting process with defining the starting point (mapping the context the script is triggered from), the routine(s) you need to perform in order to achieve the intended result.

First evaluate the task and decide whether scripting is the best way to perform it. There must be a clearly defined task or tasks for each script. The script has to be readable and easy to maintain, regardless of who the developer of the script was.The script should be efficient, achieve its objective(s) fast and with using the least amount of resources.The script should perform its task(s) and nothing else but its task(s) among all conditions it can be triggered from.Scripting philosophies and techniques might differ user by user, developer by developer, but there are a few common principles worth considering. It is worth it to rethink our approach to scripting from the ground up. has significantly modified the ways scripts can be written and tested.

Filemaker pro 11 scripting tutorial