Help

Creating a database
F
ILEMAKER PRO HELP 152
between tables in the same file and tables in external files using relationships, as explained in
Working with related tables and files. Other elements, such as scripts and access privileges, are
stored at the file level, and because of this some complex solutions will benefit from using
multiple files.
5. Determine the database tables and the data they will include, and, in turn, which fields you
will need.
Tip To make it easy to search and sort records, create separate fields for first and last name,
titles (like Mr. or Dr.) and items in addresses (city, state or province, country, and postal code).
Separating your data into multiple fields at the time of data entry can make it easier to generate
future reports. For example, using separate fields to capture transaction details such as the
date, item number, quantity, and unit price of each transaction makes it easier to compile
summary and subsummary reports at the end of a week, month, or year.
6. Decide which fields will contain common data among the tables.
For example, a database for a bakery business might include these tables: a Customers table,
which stores customer information; a Products table, which stores product information; a Line
Items table, which stores information about products sold, and an Invoices table, which stores
order information.
Each table has only one subject, and all fields in a table describe only that subject. For example,
the fields in one record of the Customers table together store all the information about one
customer. For the same reason, you might assign each customer a unique, identifying number.
You wouldn’t enter a customer identification number into the table unless you had a new
customer to add, so the existence of a customer number determines the existence of a record.
A Customers table might also have fields for the customer’s name, address and phone number.
A Products table might have fields for a product identification number, the unit price for each
product, and the quantity in stock. A Line Items table might have fields for product and invoice
identification numbers, the name, unit price, quantity, and total price of each product sold. An
Invoices table might have fields for an invoice identification number, order date, and
salesperson.
7. Determine the match fields for each table, and circle each one in your plan.
See About match fields for relationships.
Customer ID
Address
Phone
Customer Name
Country
Salesperson
Customers table
Products table
Line Items table
Order Date
Customer ID
Order Date
Invoice ID
Invoice ID
Unit Price
Product ID
Qty
Subtotal
Discount
Extended Price
Product Name
Tota l
Total in Stock
Order Date
Product ID
Unit Price
Product Name
Stock
Category
Invoices table
Region
Region
Salesperson
Discount
Total in Stock