User manual

About defining database fields
To define a new field, you give it a name. Then you select options
that determine how the field interprets, enters, calculates, stores, and
displays data. These characteristics make up the field definition.
This field stores only numbers
This field calculates a value based on
another value in the record
This field stores multiple values
ET14 Product ID
Jacket Product Name
Clothing Category
Blue Colors
$52.50 Unit Price
$5.25 Discount
Black
These fields store text
(“Discount” is 10% of “Unit Price”)
The following sections describe how to define fields using the
Define Fields dialog box.
Click to sort by
field name or type
Field names
and definitions
Type a name
for a new field
Select a field type
Click after you type a field
Choose the way fields are listed in the dialog box
name and select a field type
Creating a database 5-3
Keep these points in mind:
• You can duplicate a field definition to define a new field that’s
similar to an existing field. See “Changing field definitions” on
page 5-11.
• After you define fields, you can add them to any layout. If you
define a field in an existing file, and you don’t see it on the current
layout, be sure Add newly defined fields to current layout is selected in
Application Preferences. See“Placing and removing fields on a
layout” on page 6-15 and “Setting layout preferences” on page A-2.
• To print field definitions, see chapter 4, “Previewing and printing
information.”
About naming fields
Keep the following in mind when naming fields:
• Field names must be unique. They can contain up to 60 characters.
• Use descriptive names that clearly identify the contents of the field.
Avoid abbreviations, acronyms, or other terms that may cause
confusion.
• Don’t use the following symbols or words: , (comma) + – * / ^ &
= ≠ > < ( ) " ; (semicolon) : (colon) :: AND, OR, XOR, NOT, or a
FileMaker Pro function name. Don’t begin a field name to be used in
a calculation formula with a space, period (.), or number.
• Use _ (underscore) in place of a space to avoid restrictions in
ODBC (Open Database Connectivity), exporting, web publishing,
and other operations.
• If you’re exchanging data with another application, check the field
naming restrictions in the file formats supported by the other
application.
• If you’re using ODBC to share FileMaker data, avoid using SQL
keywords in field names. For information about ODBC, see “About
ODBC” on page 15-1.