1. Open the PlacerHills-02 database file.
2. The file will be renamed automatically to include your name. Change the project file name if directed to do so by your instructor, and save it.
3. Enable the contents in the security warning.
4. Open the Agents table in Datasheet view (Figure 2-95).

   Figure 2-95 Datasheet view of the Agents table

   1. Look at the DateHired and Phone fields. The manager of the real estate office wants those to be formatted differently.
   2. Notice that both Jack Johnstone and Kallyn Duarte have the same value in the EmployeeNum field. If the employee number is supposed to be unique, something must not be set correctly with the primary key in this table.
   3. Change Kallyn Duartes EmployeeNum to be 168, the correct value.
5. Change to Design view to make needed corrections to the Agents table.
   1. Notice that the table does not have a primary key. Although Access recommends that you assign a primary key in a table, Access lets you create a table without one.
   2. Set the EmployeeNum as the primary key.
   3. Set the Format property of the DateHired field to use Short Date.
   4. Create an input mask for the Phone field. Select the Phone Number Input Mask. Dont make any changes to the mask or placeholder character and select the Without the symbols in the mask, like this radio button. Complete the Input Mask Wizard.
   5. Change all fields to be Required.
   6. Save the table.
   7. Switch to Datasheet view to ensure that the formatting shows as desired.
   8. Adjust the field width of the DateHired field to 13. Remember that you can select the column, right-click to open the context menu and then select Field Width to change the width to a specific size.
   9. Adjust the field width of the Phone field to 16.
   10. Save and close the Agents table.
6. Open the Listings table in Datasheet view to help determine the type of relationship and the foreign key field. A one-to-many relationship exists between the Agents and Listings tables since an agent can list many different properties, but a property is listed by only one agent. The foreign key comes by taking the primary key field from the 1 table and adding it in as an additional field in the M table. In this case, the EmployeeNum should also be added into the Listings table. Notice that the Listings table has a field that stores the agents name. However, it doesnt have the foreign key. To minimize redundant data, you will change the Agent field so that it will now store the agents employee number instead of the agents name. This requires changing the data values as well as field properties.
7. Edit the data values in the Agent field in the Listings table.
   1. Click the arrow to the right of the Agent Field Name and select Sort A to Z. Because the employee name values begin with the first name, the sort isnt alphabetical by last name. However, the sort makes it easier to change the data values since all the property listings by the same agent are grouped together.
   2. Type 169 in the Agent field for Gerardo Montoya.
   3. Change each of the six records for Jack Johnstone to have the value of 160 for the Agent field. After entering the first value, you can use copy and paste to enter the remaining values.
   4. Continue changing the remaining records using the information in Table 2-35.

      Table 2-35

      This table lists the number of records to change and the agent name for the five agents in the Listings table. It also lists the data value to be typed in the Agent field.

      Number of Records to Change	Agent Name	New Value for Agent Field
      3	John Burgess	133
      5	Kallyn Duarte	168
      9	Kelly Weatherby	127
      4	Rick Chung	151
      4	Simon Bidou	103

   5. Remove the sort from the Agent field.
   6. Save the table.
8. Switch to Design view in the Listings table to edit the properties of the foreign key.
   1. Select the ListingAgent field.
   2. Change the field name to ListingAgentNumber. In this database, Placer Hills prefers that the foreign key have a unique name instead of choosing to use FKEmployeeNum as the name of the field.
   3. Change the Description to read Must match an EmployeeNum in the Agents table.
   4. Change the field size to 3.
   5. Save and close the table. Access warns you that the field size has been changed and that you may lose data. Your values meet this new size. Click Yes.
9. Create a one-to-many relationship between the Agents table and the Listings table.
   1. Open the Relationships window and add the two tables.
   2. Enlarge the table objects, if needed, to see all of the fields.
   3. Drag the EmployeeNum field from the Agents table on top of the ListingAgentNumber field in the Listings table as shown in Figure 2-96.

      Figure 2-96 Drag the EmployeeNum to the ListingAgentNumber to create a relationship

   4. Select the correct choices to Enforce Referential Integrity and Cascade Update Related Fields.
   5. Leave the Cascade Delete Related Records check box not selected. You do not want to delete property listing records just because an agent may leave the company. This enables you to keep a record of the listings.
   6. Create the relationship.
   7. Save the changes and close the Relationships window.
10. Open the Agents table in Datasheet view.
    1. Click to expand the records for Kelly Weatherby. There should be nine properties listed.
    2. Close the Agents table.
11. Preview the data records in the Listings table for printing.
    1. Select the Listings table in the Navigation Pane.
    2. Use Print Preview to show a preview of how the table will print.
    3. Change the page to Landscape orientation.
    4. Close the Print Preview.
12. Close the database.
13. Upload and save your project file.
14. Submit project for grading.