User manual
Table Of Contents
- Chapter 1 Introducing FileMaker Pro
- Chapter 2 Using databases
- About database fields and records
- Opening files
- Opening multiple windows per file
- Closing windows and files
- Saving files
- About modes
- Viewing records
- Adding and duplicating records
- Deleting records
- Entering data
- Finding records
- Making a find request
- Performing quick finds based on data in one field
- Finding text and characters
- Finding numbers, dates, times, and timestamps
- Finding ranges of information
- Finding data in related fields
- Finding empty or non-empty fields
- Finding duplicate values
- Finding records that match multiple criteria
- Finding records except those matching criteria
- Saving find requests
- Deleting and reverting requests
- Viewing, repeating, or changing the last find
- Hiding records from a found set and viewing hidden records
- Finding and replacing data
- Sorting records
- Previewing and printing databases
- Automating tasks with scripts
- Backing up database files
- Setting preferences
- Chapter 3 Creating databases
- Planning a database
- Creating a FileMaker Pro file
- Defining database fields
- Using supplemental fields
- Setting options for fields
- Defining database tables
- Creating layouts and reports
- Setting up a layout to print records in columns
- Working with objects on a layout
- Working with fields on a layout
- Working with parts on a layout
- Chapter 4 Working with related tables and files
- Chapter 5 Sharing and exchanging data
- Sharing databases on a network
- Importing and exporting data
- Saving and sending data in other formats
- Sending email messages based on record data
- Supported import/export file formats
- ODBC and JDBC
- Methods of importing data into an existing file
- About adding records
- About updating existing records
- About updating matching records
- About the importing process
- Converting a data file to a new FileMaker Pro file
- About the exporting process
- Working with external data sources
- Publishing databases on the web
- Chapter 6 Protecting databases with accounts and privilege sets
- Chapter 7 Converting databases from FileMaker Pro 6 and earlier
- Chapter 8 Security measures
- Index
About relationships | 137
Each table occurrence in the relationships graph represents a separate view into
your data. When you join two tables, you are leveraging the two existing views
to create a third view. As you add tables to your relationships, each successive
table represents an additional set of criteria that must be met before related data
can be accessed in that relationship.
You can create a relationship between any two tables in the relationships graph,
but the relationship must not create a cycle, or closed loop between tables. That
is, each series of relationships must have a starting table and an ending table,
and those tables must be different tables.
Because each relationship represents an additional set of criteria, you must be
aware of your context within the relationships graph. Context is the point in the
graph from which a relationship is evaluated. Because the graph is never a
cycle, each point along the graph offers a different perspective into your data.
Because FileMaker Pro does not permit you to create cycles within the
relationships graph, any attempt to create a cycle causes FileMaker
Pro to
generate a new, uniquely named table occurrence. A new occurrence functions
like any other occurrence in the graph and allows you to continue with your
new relationship.
For more information about the relationships graph, see Help.
About match fields for relationships
When you create a relationship between tables, you choose one or more fields
in each table as match fields. Match fields usually have common values. In a
typical relationship, a record in one table will be related to records in another
table that share a common match field value.
For example, a Customers table and an Invoices table can each use the field
Client ID to uniquely identify each customer and purchase. If the two tables are
related using Client ID as the match field, a record in the Customers table can
display a portal showing each invoice with a matching Client ID, and in the
Invoices table, each invoice with the same Client ID can display consistent
customer data.
The match fields used in a relationship can have different names. Match fields
can be any field type except container or summary.
φμπ10_υσερσ_γυιδε.βοοκ Παγε 137 Μονδαψ, Αυγυστ 25, 2008 3:59 ΠΜ