Planning a relational database
Use the relationships graph to create, change, and view the relationships in your database file. FileMaker Pro 12 Help · Contents Next > Relationships graph showing related tables and a text note Choose the object selection cursor (default cursor) Indicates that the match field is available to match many records. relaTIonal daTabaSe FiGure right or left edges (the pointer turns to a doubleheaded arrow when you hit the sweet spot), and then drag. The work FileMaker performs to deal with a one-to-many relationship is no dif- ferent from what it. In a one-to-many relationship, one record in a table can be associated with one or more records in another table. For example, each customer can have many.
Join Tables in FileMaker Pro | HomeBase Software
Think of instances where you might need Many-to-Many Relationships. In the situation I am working on, we needed a way for multiple Customers to be linked to a single Form. The form was a waiver and customers were signing up for themselves and their children at the same time on the same waiver form.
We needed a way to link the waivers not just to the parent, but also to the children.
One-to-Many Relationship Standard database relationships are created by linking ID numbers between data tables.
These fields are referred to as key fields. The image above is an example of a regular database relationship—one record the Customer can be linked to multiple Form records.
In this example a Customer record could be continuously updated with a more current form — One Customer to Many Forms. Consider the example of keeping track of invoices.
One to One relationship-primary keys
The answer is you could not. Nothing special needs to be done with the foreign key fields in the join table as they will get populated with data from the other two tables as records are created. It is not uncommon for a join table to have a lot of records in it — since records are created in the join table as records are created in the two tables it joins. In your database, this is a primary key.
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.
Determine the primary key field or fields for a multicriteria relationship for each table, and indicate each one in your plan. Then indicate the foreign key field or fields in each table. Product ID, and Line Items:: Customer ID and Line Items:: Product ID To display customer data in the Invoices table, you must have a common field between the two tables to create a relationship.
Customer ID is that common field.
In the Customers table it is the primary key; in the Invoices table it is the foreign key. In the Product ID table, this field is the primary key; in the Line Items table it is the foreign key. These key fields are a type of match field.
For each table, decide which fields will store data and which fields will be used from other related tables.