set Validation options
The default settings for a new field are to check for errors only during data entry and to allow the
For every field in the table on page 17 with one or more settings in the Validation column, remove the check mark from "Allow user to override during data entry." Doing so ensures that the validation criteria will be enforced.
For the Account Type and Description fields, click the Always radio buttoncausing these critical fields to constantly be checked for invalid data.
Strict data type, Required, Unique . These and other validation criteria are set in the Require section of the Validation tab.
Because Number fields are often used in formulas, enabling this option ensures that all data will consist only of valid
Account Type and Description are critical fields. To make them required fields, click the Not empty check box. You set this option for any database field thatif left emptywould render a record useless.
Click the Unique value check box for these fields: Bond_Serial #, CD_Certificate, Description, and Sav_Savings Account. Setting this option
set Storage options
is the only Storage option we'll apply to fields. When an index is created for a field, FileMaker continuously tracks the field's contents for all records and maintains a sorted list of those contents. Sorts and Finds performed on indexed fields are substantially faster than on non-indexed fields,
On the Storage tab of the Options dialog box, set Indexing to All for the Description field.
By default, FileMaker automatically creates indexes for fields when they're needed. You'll note that indexing has already been set to Minimal for fields to which you've applied the Unique validation option, for example. To
an index to be
Strictly speaking, since this database is
about the default layout
Now that the initial fields have been defined and you've set options for them, click OK to close the Define Database dialog box. FileMaker generates a
for the database, placing all defined fields in a single vertical column. The field
Investment Minder, however, will be an attractive, easy to use, highly functional database. Rather than use the default layout, we will create custom layouts that better serve our needs. As explained in Chapter 1, you can make as many layouts as you like, each for a different purpose. We'll create these custom layouts in the chapters that follow.