Planning a Simple Script
You never just launch into FileMaker and create databases and make fields "on the fly." If you did, you'd certainly waste lots of time later correcting your mistakes, adding fields (and then the data for them), and adapting layouts. Creating a script is very much like creating a new database. If the end result is successful, it's because you carefully considered your goals and strategies first.Begin by thinking about how you work. Ask yourself, "What things do I do in FileMaker that waste time, typing, and mouse clicks because I always have to repeat them?" Make a list of these tasks. (If nothing occurs to you at the moment, open your database and start working!) For example, you might have, "Print out a list of accounts over 30 days past due."You should temporarily skip any tasks that require you to choose between options at some point in the process (we'll get to those later). Of the tasks that remain, look for one that mostly involves several menu commands in sequence. Make a list of the main menu bar commands you choose when you do the task, in the order in which you do them.When we look at the steps we take to get our overdue accounts statement, our list contains:
- Find recordsSort recordsGo to the overdue accounts layoutPrint the layout
- Find recordsSort recordsGo to the overdue accounts layoutSet the printing optionsPrint the layoutThere's one last step that you might not think about when you look at your process. Once you've finished printing, you don't usually need the printing layout on the screen. In fact, you probably want to return to whatever you were doing before you printed the overdue accounts statement. So the last step in the list should be:Go back to where you started
