Relationships: Your Key to Data Integrity in Access 2003

Date: Jan 9, 2004

Sample Chapter is provided courtesy of Sams.

Return to the article

In This Chapter

• Why This Chapter Is Important

• Introduction to Relational Database Design

• Establishing Relationships in Access

• Establishing Referential Integrity

• Looking at the Benefits of Relationships

• Examining Indexes and Relationships

• Practical Examples: Establishing the Relationships Between the Tables Included in the Time and Billing Database

Why This Chapter Is Important

A relationship exists between two tables when one or more key fields from one table are matched to one or more key fields in another table. The fields in both tables usually have the same name, data type, and size. Relationships are a necessary by-product of the data normalization process. Data normalization, which was introduced in Chapter 1, "Access as a Development Tool," and is covered in additional detail in this chapter, is the process of eliminating duplicate information from your system by splitting information into several tables, each containing a unique value (primary key). Although data normalization brings many benefits, you need to relate your application's tables to each other so that your users can view the data in the system as a single entity. After you define relationships between tables, you can build queries, forms, reports, and data access pages that combine information from multiple tables. In this way, you can reap all the benefits of data normalization while ensuring that your system provides users with all the information they need.

Many people believe Access is such a simple product to use that database design is something they don't need to worry about. I couldn't disagree more! Just as a house without a foundation will fall over, a database with poorly designed tables and relationships will fail to meet the needs of its users.

The History of Relational Database Design

Dr. E.F. Codd first introduced formal relational database design in 1969 while he was at IBM. Relational theory, which is based on set theory, applies to both databases and database applications. Codd developed 12 rules that determine how well an application and its data adhere to the relational model. Since Codd first conceived these 12 rules, the number of rules has expanded into the hundreds. (Don't worry, you only need to learn a few of them!)

You should be happy to learn that, although not perfect as an application development environment, Microsoft Access measures up quite well as a relational database system.

Goals of Relational Database Design

The number one goal of relational database design is to, as closely as possible, develop a database that models some real-world system. This involves breaking the real-world system into tables and fields, and determining how the tables relate to each other. Although on the surface this might appear to be a trivial task, it can be an extremely cumbersome process to translate a real-world system into tables and fields.

A properly designed database has many benefits. The processes of adding, editing, deleting, and retrieving table data are greatly facilitated by a properly designed database. In addition, reports are easier to build. Most importantly, the database becomes easy to modify and maintain.

Rules of Relational Database Design

To adhere to the relational model, certain rules must be followed. These rules determine what is stored in a table, and how the tables are related.

The Rules of Tables

Each table in a system must store data about a single entity. An entity usually represents a real-life object or event. Examples of objects are customers, employees, and inventory items. Examples of events include orders, appointments, and doctor visits.

The Rules of Uniqueness and Keys

Tables are composed of rows and columns. To adhere to the relational model, each table must contain a unique identifier. Without a unique identifier, it becomes programmatically impossible to uniquely address a row. You guarantee uniqueness in a table by designating a primary key, which is a single column or a set of columns that uniquely identifies a row in a table.

Each column or set of columns in a table that contains unique values is considered a candidate key. One candidate key becomes the primary key. The remaining candidate keys become alternate keys. A primary key made up of one column is considered a simple key. A primary key comprising multiple columns is considered a composite key.

It is generally a good idea to pick a primary key that is

• Minimal (has as few columns as possible)

• Stable (rarely changes)

• Simple (familiar to the user)

Following these rules greatly improves the performance and maintainability of your database application, particularly if you are dealing with large volumes of data.

Consider the example of an employee table. An employee table is generally composed of employee-related fields such as Social Security number, first name, last name, hire date, salary, and so on. The combination of the first name and the last name fields could be considered a primary key. This choice might work, until the company hires two employees with the same name. Although the first and last names could be combined with additional fields to constitute uniqueness (for example, hire date), this would violate the rule of keeping the primary key minimal. Furthermore, an employee might get married and her last name might change. This violates the rule of keeping a primary key stable.

Using a name as the primary key violates the principle of stability. The Social Security number might be a valid choice, but a foreign employee might not have a Social Security number. This is a case where a derived, rather than a natural, primary key is appropriate. A derived key is an artificial key that you create. A natural key is one that is already part of the database.

In examples such as this, I suggest adding EmployeeID as an AutoNumber field. Although the field would violate the rule of simplicity (because an employee number is meaningless to the user), it is both small and stable. Because it is numeric, it is also efficient to process. In fact, I use AutoNumber fields (an Identity field in SQL Server) as primary keys for most of the tables that I build.

The Rules of Foreign Keys and Domains

A foreign key in one table is the field that relates to the primary key in a second table. For example, the CustomerID is the primary key in the Customers table. It is the foreign key in the Orders table.

A domain is a pool of values from which columns are drawn. A simple example of a domain is the specific data range of employee hire dates. In the case of the Orders table, the domain of the CustomerID column is the range of values for the CustomerID in the Customers table.

Normalization and Normal Forms

Some of the most difficult decisions that you face as a developer are what tables to create, and what fields to place in each table, as well as how to relate the tables that you create. Normalization is the process of applying a series of rules to ensure that your database achieves optimal structure. Normal forms are a progression of these rules. Each successive normal form achieves a better database design than the previous form did. Although there are several levels of normal forms, it is generally sufficient to apply only the first three levels of normal forms. The following sections describe the first three levels of normal forms.

First Normal Form

To achieve first normal form, all columns in a table must be atomic. This means, for example, that you cannot store first names and last names in the same field. The reason for this rule is that data becomes very difficult to manipulate and retrieve if multiple values are stored in a single field. Using the full name as an example, it would become impossible to sort by first name or last name independently if both values are stored in the same field. Furthermore, you or the user must perform extra work to extract just the first name or the last name from the field.

Another requirement for first normal form is that the table must not contain repeating values. An example of repeating values is a scenario in which the Item1, Quantity1, Item2, Quantity2, Item3, and Quantity3 fields are all found within the Orders table (see Figure 3.1). This design introduces several problems. What if the user wants to add a fourth item to the order? Furthermore, finding the total ordered for a product requires searching several columns. In fact, all numeric and statistical calculations on the table become extremely cumbersome. The alternative, shown in Figure 3.2, achieves first normal form. Notice that each item ordered is located in a separate row.

Figure 3.1 This table contains repeating groups. Repeating groups make it difficult to summarize and manipulate table data.

Figure 3.2 This table achieves first normal form. Notice that all fields are atomic, and that it contains no repeating groups.

Second Normal Form

To achieve second normal form, all non-key columns must be fully dependent on the primary key. In other words, each table must store data about only one subject. Notice the table shown in Figure 3.2. It includes information about the order (OrderID, CustomerID, and OrderDate) and information about the items the customer is ordering (Item and Quantity). To achieve second normal form, you must break this data into two tables: an order table and an order detail table. The process of breaking the data into two tables is called decomposition. It is considered to be non-loss decomposition because no data is lost during the decomposition process. After you separate the data into two tables, you can easily bring the data back together by joining the two tables in a query. Figure 3.3 shows the data separated into two tables. These two tables achieve second normal form.

Figure 3.3 These tables achieve second normal form. The fields in each table pertain to the primary key of the table.

Third Normal Form

To attain third normal form, a table must meet all the requirements for first and second normal form, and all non-key columns must be mutually independent. This means that you must eliminate any calculations, and you must break out data into lookup tables.

An example of a calculation stored in a table is the product of price multiplied by quantity. Instead of storing the result of this calculation in the table, you would generate the calculation in a query, or in the control source of a control on a form or a report.

The example in Figure 3.3 does not achieve third normal form because the description of the inventory items is stored in the order details table. If the description changes, all rows with that inventory item need to be modified. The order detail table, shown in Figure 3.4, shows the item descriptions broken into an inventory table. This design achieves third normal form. All fields are mutually independent. You can modify the description of an inventory item in one place.

Figure 3.4 This table on the right achieves third normal form. We have moved the description of the inventory items to an inventory table, and the ItemID is stored in the order details table.

Denormalization—Purposely Violating the Rules

Although the developer's goal is normalization, there are many times when it makes sense to deviate from normal forms. We refer to this process as denormalization. The primary reason for applying denormalization is to enhance performance.

An example of when denormalization might be the preferred tact could involve an open invoices table and a summarized accounting table. It might be impractical to calculate summarized accounting information for a customer when we need it. Instead we can maintain the summary calculations in a summarized accounting table so that we can easily retrieve them as needed. Although the upside of this scenario is improved performance, the downside is that we must update the summary table whenever we make changes to the open invoices. This imposes a definite trade-off between performance and maintainability. You must decide whether the trade-off is worth it.

If you decide to denormalize, document your decision. Make sure that you make the necessary application adjustments to ensure that you properly maintain the denormalized fields. Finally, test to ensure that the denormalization process actually improves performance.

Integrity Rules

Although integrity rules are not part of normal forms, they are definitely part of the database design process. Integrity rules are broken into two categories. They include overall integrity rules and database-specific integrity rules.

Overall Rules

The two types of overall integrity rules are referential integrity rules and entity integrity rules. Referential integrity rules dictate that a database does not contain any orphan foreign key values. This means that

• Child rows cannot be added for parent rows that do not exist. In other words, an order cannot be added for a nonexistent customer.

• A primary key value cannot be modified if the value is used as a foreign key in a child table. This means that a CustomerID in the customers table cannot be changed if the orders table contains rows with that CustomerID.

• A parent row cannot be deleted if child rows are found with that foreign key value. For example, a customer cannot be deleted if the customer has orders in the order table.

Entity integrity dictates that the primary key value cannot be Null. This rule applies not only to single-column primary keys, but also to multi-column primary keys. In fact, in a multi-column primary key, no field in the primary key can be Null. This makes sense because, if any part of the primary key can be Null, the primary key can no longer act as a unique identifier for the row. Fortunately, the Jet Engine (Access's database engine) does not allow a field in a primary key to be Null.

Database-Specific Rules

The other set of rules applied to a database are not applicable to all databases, but are, instead, dictated by business rules that apply to a specific application. Database-specific rules are as important as overall integrity rules. They ensure that only valid data is entered into a database. An example of a database-specific integrity rule is that the delivery date for an order must fall after the order date.

Examining the Types of Relationships

Three types of relationships can exist between tables in a database: one-to-many, one-to-one, and many-to-many. Setting up the proper type of relationship between two tables in your database is imperative. The right type of relationship between two tables ensures

• Data integrity

• Optimal performance

• Ease of use in designing system objects

The reasons behind these benefits are covered throughout this chapter. Before you can understand the benefits of relationships, though, you must understand the types of relationships available.

One-to-Many

A one-to-many relationship is by far the most common type of relationship. In a one-to-many relationship, a record in one table can have many related records in another table. A common example is a relationship set up between a Customers table and an Orders table. For each customer in the Customers table, you want to have more than one order in the Orders table. On the other hand, each order in the Orders table can belong to only one customer. The Customers table is on the one side of the relationship, and the Orders table is on the many side. For you to implement this relationship, the field joining the two tables on the one side of the relationship must be unique.

In the Customers and Orders tables example, the CustomerID field that joins the two tables must be unique within the Customers table. If more than one customer in the Customers table has the same customer ID, it is not clear which customer belongs to an order in the Orders table. For this reason, the field that joins the two tables on the one side of the one-to-many relationship must be a primary key or have a unique index. In almost all cases, the field relating the two tables is the primary key of the table on the one side of the relationship. The field relating the two tables on the many side of the relationship is the foreign key.

One-to-One

In a one-to-one relationship, each record in the table on the one side of the relationship can have only one matching record in the table on the many side of the relationship. This relationship is not common, and is used only in special circumstances. Usually, if you have set up a one-to-one relationship, you should have combined the fields from both tables into one table. The following are the most common reasons why you should create a one-to-one relationship:

• The number of fields required for a table exceeds the number of fields allowed in an Access table.

• Certain fields that are included in a table need to be much more secure than other fields included in the same table.

• Several fields in a table are required for only a subset of records in the table.

The maximum number of fields allowed in an Access table is 255. There are very few reasons why a table should ever have more than 255 fields. In fact, before you even get close to 255 fields, you should take a close look at the design of your system. On the rare occasion when having more than 255 fields is appropriate, you can simulate a single table by moving some of the fields to a second table and creating a one-to-one relationship between the two tables.

The second reason to separate into two tables data that logically would belong in the same table involves security. An example is a table containing employee information. Certain information, such as employee name, address, city, state, ZIP Code, home phone, and office extension, might need to be accessed by many users of the system. Other fields, including the hire date, salary, birth date, and salary level, might be highly confidential. Field-level security is not available in Access. You can simulate field-level security by using a special attribute of queries called Run with Owner's Permissions. Chapter 11, "Advanced Query Techniques," covers this feature.

The alternative to this method is to place the fields that all users can access in one table and the highly confidential fields in another. You give only a special Admin user (a user with special security privileges, not one actually named Admin) access to the table containing the confidential fields. You can then use ActiveX Data Objects (ADO) code to display the fields in the highly confidential table when needed. You accomplish this using a query with Run with Owner's Permissions, based on the special Admin user's permission to the highly secured table. Chapter 28, "Advanced Security Techniques," covers this technique in more detail.

The last situation in which you would want to define one-to-one relationships is when you will use certain fields in a table for only a relatively small subset of records. An example is an Employee table and a Vesting table. Certain fields are required only for employees who are vested. If only a small percentage of a company's employees are vested, it is not efficient, in terms of performance or disk space, to place all the fields containing information about vesting in the Employee table. This is especially true if the vesting information requires a large volume of fields. By breaking the information into two tables and creating a one-to-one relationship between them, you can reduce disk-space requirements and improve performance. This improvement is particularly pronounced if the Employee table is large.

Many-to-Many

In a many-to-many relationship, records in both tables have matching records in the other table. You cannot directly define a many-to-many relationship in Access; you must develop this type of relationship by adding a table called a junction table. You relate the junction table to each of the two tables in one-to-many relationships. An example is an Orders table and a Products table. Each order probably will contain multiple products, and each product is found on many different orders. The solution is to create a third table called OrderDetails. You relate the OrderDetails table to the Orders table in a one-to-many relationship based on the OrderID field. You relate it to the Products table in a one-to-many relationship based on the ProductID field.

You use the Relationships window to establish relationships between Access tables, as shown in Figure 3.5. To open the Relationships window, click Relationships on the toolbar with the Database window active or choose Relationships from the Tools menu. If you have not established any relationships, the Show Table dialog appears. The Show Table dialog allows you to add tables to the Relationships window.

Looking at the Relationships window, you can see the type of relationships that exists for each table. All the one-to-many and one-to-one relationships defined in a database are represented with a join line. If you enforce referential integrity between the tables involved in a one-to-many relationship, the join line between the tables appears with the number 1 on the one side of the relationship and with an infinity symbol (x) on the many side of the relationship. One-to-one relationships appear with a 1 on both ends of the join lines.

Figure 3.5 The Relationships window enables you to view, add, modify, and remove relationships between tables.

Establishing a Relationship Between Two Tables

To establish a relationship between two tables, follow these six steps:

1. Open the Relationships window.

2. If it is the first time that you're opening the Relationships window of a particular database, the Show Table dialog appears. Select each table you want to relate and click Add.

3. If you have already established relationships in the current database, the Relationships window appears. If the tables you want to include in the relationship do not appear, click the Show Table button on the toolbar or choose Show Table from the Relationships menu. To add the desired tables to the Relationships window, select a table, and then click Add. Repeat this process for each table you want to add. To select multiple tables at once, press Shift while clicking to select contiguous tables or press Ctrl while clicking to select noncontiguous tables; then click Add. Click Close when you are finished.

4. Click and drag the field from one table to the matching field in the other table. The Edit Relationships dialog appears, as shown in Figure 3.6.

5. Determine whether you want to establish referential integrity, and whether you want to cascade update related fields or cascade delete related records by enabling the appropriate check boxes. The section later in this chapter entitled "Establishing Referential Integrity" covers these topics.

6. Click Create.

Figure 3.6 The Edit Relationships dialog enables you to view and modify the relationships between the tables in a database.

Looking at Guidelines for Establishing Relationships

You must remember a few important things when establishing relationships. If you are not aware of these important gotchas, you could find yourself in some pretty hairy situations.

• It is important to understand the correlation between the Relationships window and the actual relationships you have established within the database. The Relationships window lets you view and modify the existing relationships. When you establish relationships, Access creates the relationships the moment you click Create. You can delete the tables from the Relationships window (by selecting them and pressing Delete), but the relationships still will exist. (The "Modifying an Existing Relationship" section, which appears later in this chapter, covers the process of permanently removing relationships.) The Relationships window provides a visual blueprint of the relationships that you have established. If you modify the layout of the window by moving tables around, or by adding/removing tables to the window, Access prompts you to save the layout after you close the Relationships window. Access is not asking whether you want to save the relationships you have established; it is simply asking whether you want to save the visual layout of the window.

• When adding tables to the Relationships window using the Show Tables dialog, it is easy to accidentally add the same table to the window many times. This is because the tables you are adding can hide behind the Show Tables dialog, or they can appear below the portion of the Relationships window that you are viewing. If this occurs, you'll see multiple occurrences of the same table when you close the Show Tables dialog. Access gives each occurrence of the table a different alias. You must remove the extra occurrences.

• You also can add queries to the Relationships window by using the Show Tables dialog. Although rarely used, this might be useful if you regularly include the same queries within other queries and want to permanently establish a relationship between them.

• If you remove tables from the Relationships window (this does not delete the relationships) and you want to once again show all relationships that exist in the database, click Show All Relationships on the toolbar or choose Show All from the Relationships menu. These processes show all existing relationships.

• To delete a relationship, click the join line and press Delete.

Create a new database and add a table called tblCustomers, another called tblOrders, and a third called tblOrderDetails. The tables should have the following fields:

tblCustomers: CustomerID, CompanyName, Address, City, State, ZipCode

tblOrders: OrderID, CustomerID, OrderDate, ShipVIA

tblOrderDetails: OrderID, LineNumber, ItemID, Quantity, Price

1. In the tblCustomers table, make the CustomerID field a Text field. Designate the CustomerID field as the primary key. Set the size of the field to 5. Make all other fields Text fields with their default properties.

2. In the tblOrders table, set OrderID to the AutoNumber field type. Make the OrderID the primary key field. Make the CustomerID field a Text field with a field size of 5. Set the field type of the OrderDate field to Date, and the field type of the ShipVIA field to Number with a size of Long Integer.

3. In the tblOrderDetails table, set the field type of the OrderID field to Number and make sure that the size is Long Integer. Set the field type of the LineNumber field to Number with a size of Long Integer. You should base the primary key of the table on the combination of the OrderID and LineNumber fields. The ItemID and Quantity fields should be the Number type with a size of Long Integer. The Price field should be the Currency type.

4. To open the Relationships window, click Relationships on the toolbar with the Database window active. With the tblCustomers table in the Show Table dialog selected, hold down your Shift key and click to select the tblOrders table. Click Add. All three tables should appear in the Relationships window. Click Close. Click and drag from the CustomerID field in the tblCustomers table to the CustomerID field in the tblOrders table. After the Relationships dialog appears, click Create. Repeat the process, clicking and dragging the OrderID field from the tblOrders table to the OrderID field in the tblOrderDetails table.

Modifying an Existing Relationship

Modifying an existing relationship is easy. Access gives you the capability to delete an existing relationship or to simply modify the nature of the relationship. To permanently remove a relationship between two tables, follow these three steps:

1. With the Database window active, click Relationships on the toolbar.

2. Click the line joining the two tables whose relationship you want to delete.

3. Press Delete. Access prompts you to verify your actions. Click Yes.

You often will want to modify the nature of a relationship rather than remove it. To modify a relationship, follow these four steps:

1. With the Database window active, click Relationships on the toolbar.

2. Double-click the line joining the two tables whose relationship you want to modify.

3. Make the required changes.

4. Click OK. All the normal rules regarding the establishment of relationships will apply.

As you can see, establishing a relationship is quite easy. Establishing the right kind of relationship is a little more difficult. When you attempt to establish a relationship between two tables, Access makes some decisions based on a few predefined factors:

• Access establishes a one-to-many relationship if one of the related fields is a primary key or has a unique index.

• Access establishes a one-to-one relationship if both the related fields are primary keys or have unique indexes.

• Access creates an indeterminate relationship if neither of the related fields is a primary key, and neither has a unique index. You cannot establish referential integrity in this case.

As covered earlier in the chapter, referential integrity consists of a series of rules that the Jet Engine applies to ensure that it properly maintains the relationships between tables. At the most basic level, referential integrity rules prevent the creation of orphan records in the table on the many side of the one-to-many relationship. After establishing a relationship between a Customers table and an Orders table, for example, all orders in the Orders table must be related to a particular customer in the Customers table. Before you can establish referential integrity between two tables, the following conditions must be met:

• The matching field on the one side of the relationship must be a Primary Key field or must have a unique index.

• The matching fields must have the same data types (for linking purposes, AutoNumber fields match Long Integer fields). With the exception of Text fields, they also must have the same size. Number fields on both sides of the relationship must have the same size (Long Integer, for example).

• Both tables must be part of the same Access database.

• Both tables must be stored in the proprietary Access file (.MDB) format (they cannot be external tables from other sources).

• The database containing the two tables must be open.

• Existing data within the two tables cannot violate any referential integrity rules. All orders in the Orders table must relate to existing customers in the Customers table, for example.

After you establish referential integrity between two tables, the Jet Engine applies the following rules:

• You cannot enter a value in the foreign key of the related table that does not exist in the primary key of the primary table. For example, you cannot enter a value in the CustomerID field of the Orders table that does not exist in the CustomerID field of the Customers table.

• You cannot delete a record from the primary table if corresponding records exist in the related table. For example, you cannot delete a customer from the Customers table if related records exist in the Orders table (records with the same value in the CustomerID field).

• You cannot change the value of a primary key on the one side of a relationship if corresponding records exist in the related table. For example, you cannot change the value in the CustomerID field of the Customers table if corresponding orders exist in the Orders table.

If you attempt to violate any of the previous three rules and you have enforced referential integrity between the tables, Access displays an appropriate error message, as shown in Figure 3.7.

Figure 3.7 An error message when attempting to add an order for a customer who doesn't exist.

The Jet Engine's default behavior is to prohibit the deletion of parent records that have associated child records and to prohibit the change of a primary key value of a parent record when that parent has associated child records. You can override these restrictions by using the two check boxes available in the Relationships dialog when you establish or modify a relationship.

The following example enforces referential integrity between the tblCustomers table and the tblOrders table. It illustrates how this affects the process of adding and deleting records.

1. To open the Relationships window, select the Database window and click Relationships on the toolbar. Double-click the join line between tblCustomers and tblOrders. Enable the Enforce Referential Integrity check box. Click OK. Repeat the process for the relationship between tblOrders and tblOrderDetails.

2. Go into tblCustomers and add a couple of records. Take note of the customer IDs. Go into tblOrders. Add a couple of records, taking care to assign customer IDs of customers that exist in the tblCustomers table. Now try to add an order for a customer whose customer ID does not exist in tblCustomers. You should get an error message.

3. Attempt to delete a customer from tblCustomers who does not have any orders. You should get a warning message, but Access should allow you to complete the process. Now try to delete a customer who does have orders. The Jet Engine should prohibit you from deleting the customer. Attempt to change the customer ID of a customer who has orders. You should not be able to do this.

Cascade Update Related Fields

The Cascade Update Related Fields option is available only if you have established referential integrity between the tables. With this option selected, the user can change the primary key value of the record on the one side of the relationship. When the user tries to modify the field joining the two tables on the one side of the relationship, the Jet Engine cascades the change down to the foreign key field on the many side of the relationship. This is useful if the primary key field is modifiable. For example, a purchase number on a purchase order master record might be updatable. If the user modifies the purchase order number of the parent record, you would want to cascade the change to the associated detail records in the purchase order detail table.

Figure 3.8 An orphan record with Null in the foreign key field.

Cascade Delete Related Records

The Cascade Delete Related Records option is available only if you have established referential integrity between the tables. With this option selected, the user can delete a record on the one side of a one-to-many relationship, even if related records exist in the table on the many side of the relationship. A user can delete a customer even if the customer has existing orders, for example. The Jet Engine maintains referential integrity between the tables because it automatically deletes all related records in the child table.

If you attempt to delete a record from the table on the one side of a one-to-many relationship and no related records exist in the table on the many side of the relationship, you get the usual warning message, as shown in Figure 3.9. On the other hand, if you attempt to delete a record from the table on the one side of a one-to-many relationship and related records exist in the child table, Access warns you that you are about to delete the record from the parent table, as well as any related records in the child table (see Figure 3.10).

Figure 3.9 A message that appears after the user attempts to delete a parent record without related child records.

Figure 3.10 A message that appears after the user attempts to delete a parent record with related child records.

With the Cascade Update feature enabled, you are able to update the primary key value of a record that has associated child records. With the Cascade Delete feature enabled, you can delete a parent record that has associated child records. This exercise illustrates the use of Cascade Update and Cascade Delete.

1. Modify the relationship between tblCustomers and tblOrders. Enable the Cascade Update Related Fields check box. Modify the relationship between tblOrders and tblOrderDetails. Enable the Cascade Delete Related Records check box. There is no need to enable Cascade Update Related Fields because the OrderID field in tblOrders is an AutoNumber field.

2. Attempt to delete a customer who has orders. The Jet Engine should still prohibit you from doing this because you did not enable Cascade Delete Related Records. Change the customer ID in tblCustomers of a customer who has orders. The Jet Engine should allow this change. Take a look at the tblOrders table. The Jet Engine should have updated the customer ID of all corresponding records in the table to reflect the change in the parent record.

3. Add some order details to the tblOrderDetails table. Try to delete any order that has details within the tblOrderDetails table. You should receive a warning, but the Jet Engine should allow you to complete the process.

The primary benefit of relationships is the data integrity they provide. Without the establishment of relationships, users are free to add records to child tables without regard to entering required parent information. After referential integrity is established, you can enable Cascade Update Related Fields or Cascade Delete Related Records, as appropriate, which will save you quite a bit of code in maintaining the integrity of the data in your system. Most relational database management systems require that you write the code to delete related records when the user deletes a parent record or to update the foreign key in related records when the user modifies the primary key of the parent. By enabling the Cascade Update and Cascade Delete check boxes, you are sheltered from having to write a single line of code to perform these tasks when they are appropriate.

Access automatically carries relationships into your queries. This means that each time you build a new query, it automatically establishes the relationships between the tables within the query, based on the relationships you have set up in the Relationships window. Furthermore, each time you build a form or report, Access uses relationships between the tables included on the form or report to assist with the design process. Whether you delete or update data using a datasheet or a form, all referential integrity rules automatically apply, even if you establish the relationship after you build the form.

The field that joins two tables on the one side of a one-to-many relationship must be a primary key field or must have a unique index so that the Jet Engine can maintain referential integrity. If the index on the one side of the relationship is not unique, there is no way to determine to which parent a child record belongs.

In Access 2003, it is not necessary to create an index for the field on the many side of the relationship. Access 2003 will create an internal index for you. If you do create an index on the many side of the relationship, make sure that you set the index to Yes (Duplicates OK); otherwise, you will have a one-to-one, rather than a one-to-many, relationship.

In this example, you'll establish some of the relationships you need to set up for the tables included in a hypothetical time and billing database. If you would like to build the relationships yourself, open the database that you created in Chapter 2, "What Every Developer Needs to Know About Databases and Tables."

• tblClients to tblProjects—You need to relate tblClients and tblProjects in a one-to-many relationship based on the ClientID field. You must enforce referential integrity to ensure that the user cannot add projects for nonexistent clients. There is no need to set Cascade Update Related Fields because the client ID that relates the two tables is an AutoNumber field in tblClients. You do not want to enable Cascade Delete Related Records because you do not want any billing information to change if the user deletes a client. Instead, you want to prohibit the deletion of clients who have projects by establishing referential integrity between the two tables.

• tblProjects to tblPayments—You need to relate tblProjects and tblPayments in a one-to-many relationship based on the ProjectID field. You must enforce referential integrity to ensure that the user cannot add payments for nonexistent projects. There is no need to set Cascade Update Related Fields because the ProjectID that relates the two tables is an AutoNumber field in tblProjects. You do not want to enable Cascade Delete Related Records because you do not want any payment information to change if the user deletes a client. Prohibit the deletion of clients who have payments by establishing referential integrity between the two tables.

• tblProjects to tblTimeCardHours—You need to relate tblProjects and tblTimeCardHours in a one-to-many relationship based on the ProjectID field. You must enforce referential integrity to ensure that the user cannot add hours for nonexistent projects. There is no need to set Cascade Update Related Fields because the ProjectID that relates the two tables is an AutoNumber field in tblProjects. Enable Cascade Delete Related Records so that the Jet Engine deletes the associated hours if the user deletes a project.

• tblProjects to tblTimeCardExpenses—You need to relate tblProjects and tblTimeCardExpenses in a one-to-many relationship based on the ProjectID field. You must enforce referential integrity to ensure that the user cannot add expenses for nonexistent projects. There is no need to set Cascade Update Related Fields because the ProjectID that relates the two tables is an AutoNumber field in tblProjects. Enable Cascade Delete Related Records so that the Jet Engine deletes expenses if the user deletes a project.

• tblEmployees to tblTimeCards—You need to relate tblEmployees and tblTimeCards in a one-to-many relationship based on the EmployeeID field. You must enforce referential integrity to ensure that the user cannot add time cards for nonexistent employees. There is no need to set Cascade Update Related Fields because the EmployeeID that relates the two tables is an AutoNumber field in tblEmployees. You do not want to enable Cascade Delete Related Records because, if the user deletes an employee, you do not want the Jet Engine to delete all the employee's time cards.

• tblEmployees to tblProjects—You need to relate tblEmployees and tblProjects in a one-to-many relationship based on the EmployeeID field. You must enforce referential integrity to ensure that the user cannot assign projects to nonexistent employees. There is no need to set Cascade Update Related Fields because the employee ID that relates the two tables is an AutoNumber field in tblEmployees. You do not want to enable Cascade Delete Related Records because, if the user deletes an employee, you do not want the Jet Engine to delete all the employee's projects, which is generally not desirable.

• tblTimeCards to tblTimeCardHours—You need to relate tblTimeCards and tblTimeCardHours in a one-to-many relationship based on the TimeCardID field. You must enforce referential integrity to ensure that the user cannot add time card hours for nonexistent time cards. There is no need to set Cascade Update Related Fields because the time card ID that relates the two tables is an AutoNumber field in tblTimeCards. You do want to enable Cascade Delete Related Records because, if the user deletes a time card, you want the Jet Engine to delete the corresponding hours.

• tblTimeCards to tblTimeCardExpenses—You need to relate tblTimeCards and tblTimeCardExpenses in a one-to-many relationship based on the TimeCardID field. You must enforce referential integrity to ensure that the user cannot add time card expenses for nonexistent time cards. There is no need to set Cascade Update Related Fields because the time card ID that relates the two tables is an AutoNumber field in tblTimeCards. You do want to enable Cascade Delete Related Records because, if the user deletes a time card, you want the Jet Engine to delete the corresponding expenses.

• tblExpenseCodes to tblTimeCardExpenses—You need to relate tblExpenseCodes and tblTimeCardExpenses in a one-to-many relationship based on the ExpenseCodeID field. You must enforce referential integrity to ensure that the user cannot add time card expenses with nonexistent expense codes. There is no need to set Cascade Update Related Fields because the expense code ID that relates the two tables is an AutoNumber field in tblExpenseCodes. You do not want to enable Cascade Delete Related Records because, if the user deletes an expense code, you do not want the Jet Engine to delete the corresponding expenses.

• tblWorkCodes to tblTimeCardHours—You need to relate tblWorkCodes and tblTimeCardHours in a one-to-many relationship based on the WorkCodeID field. You must enforce referential integrity to ensure that the user cannot add time card hours with invalid work codes. There is no need to set Cascade Update Related Fields because the work code ID that relates the two tables is an AutoNumber field in tblWorkCodes. You do not want to enable Cascade Delete Related Records because, if the user deletes a work code, you do not want the Jet Engine to delete the corresponding hours.

• tblPaymentMethods to tblPayments—You need to relate tblPaymentMethods and tblPayments in a one-to-many relationship based on the PaymentMethodID field. You must enforce referential integrity to ensure that the user cannot add payments with an invalid payment method. There is no need to set Cascade Update Related Fields because the PaymentMethodID that relates the two tables is an AutoNumber field in tblPaymentMethods. You do not want to enable Cascade Delete Related Records because, if the user deletes a payment method, you do not want the Jet Engine to delete the corresponding payments.

Relationships enable you to normalize your database. Using relationships, you can divide your data into separate tables, once again combining the data at runtime. This chapter began by explaining relational database design principles. It described the types of relationships that you can define. It then covered the details of establishing and modifying relationships between tables and described all the important aspects of establishing relationships.

The capability to easily establish and maintain referential integrity between tables is an important strength of Microsoft Access. This chapter described the referential integrity options and highlighted when each option is appropriate. Finally, this chapter summarized the benefits of relationships.

© 2025 Pearson Education, Informit. All rights reserved.

800 East 96th Street, Indianapolis, Indiana 46240