Database Reference
In-Depth Information
Flush Cache to Disk
Any time changes are made to a record, FileMaker records those changes in your computer's
memory first and writes the change to the hard drive later—when it gets some free time. If
you want to
force
the changes to be written to disk immediately, then you can run the
Flush
Cache to Disk
script step. For instance, you might add this script step after a script that cre-
ates a new customer order. That way, if your computer crashes while you're busily taking or-
ders, then you lose only the last order you were working on. It's also commonly used to re-
Window-Related Script Steps
)
isn't doing its job. This script step can really bog down per-
formance, especially on databases shared using WebDirect (
Server Hardware
)
. Use it spar-
ingly. In most cases, the
Refresh Object
step is a better choice for maintaining speed.
Figure 12-22. Once you prepare your computer, and select an ODBC data source, the source name
shows up beside the top Specify button. Then you can use the Calculations dialog box to assemble a
query, or just type directly in the SQL text field. The query shown here grabs the First Name, Last
Name, and Email Address data for every customer record where the status is dynamic. The data
would be sorted by Last Name and subsorted by First Name, all in ascending order.
Exit Application
Last but not least, you can have a script exit or quit the FileMaker program on your behalf.
Of course, this causes every open window and file to be closed as well. People usually use
this script step when they have just one database, and they never use FileMaker unless
they're in that database. They add the
Exit Application
step to the very end of their data-
