Filemaker Pro 10 TU692LL/A Benutzerhandbuch

Produktcode
TU692LL/A
Seite von 82
8     FileMaker Pro Tutorial
Where to find the sample file
The sample file contains data for the Corporate Travelers Club and provides a place for you to practice 
building the database elements that are described in each lesson. If you need to start over, replace your 
existing sample file with a new copy. If the sample file was installed, it is in:
FileMaker Pro 10/English Extras/Tutorial
or
FileMaker Pro 10 Advanced/English Extras/Tutorial
You can also download the sample file from the FileMaker website by visiting 
 
www.filemaker.com/documentation.
Database concepts
What is a database?
database is a method of organizing and analyzing information. You’ve probably used several databases 
recently without realizing it. A date book, a parts list, and even your own address book are databases.
Why use a database?
Storing information in a database file has many benefits. A database doesn’t just hold information—it helps 
you organize and analyze the information in different ways. For example, databases allow you to group 
information for reports, sort information for mailing labels, count your inventory, or find a particular invoice.
Computerized databases offer many additional advantages over their paper-based counterparts: speed, 
reliability, precision, and the ability to automate many repetitive tasks.
How is a database organized?
A database file is organized into one or more tables. Tables store records. Each record is a collection of 
fields.
Imagine your address book is a FileMaker Pro database file. Each listing in your address book is one record 
in an Address Book table. Each record has information, such as name, address, city, and so on. Each of these 
pieces of information—name, address, and city—is stored in a separate field. 
How is field data displayed?
FileMaker Pro displays fields on layouts. Each layout is based on a single table, and displays records from 
that table.
Imagine that your database has a Tasks table in addition to the Address Book table. A layout based on the 
Address Book table will display fields and records from the Address Book table. A layout based on the Tasks 
table will display fields and records from the Tasks table.