ERDs in MS Access

  • Implementing ER Diagram Relationships

    Eventually ERDs are mapped to database tables with primary keys and foreign keys. This process is called table mapping; or, in other words, we are implementing the ERD in a relational database management system (DBMS). You might remember that we did this once in at the end of the first chapter in this database module. When the ERD is implemented in a DBMS, another diagram is created that looks quite similar to the ERDs we created in Lucidchart (or on paper) with a few important differences.

  • Referential Integrity

    Hopefully you noticed in the prior video the concept of referential integrity. Referential Integrity is a property of data which, when satisfied, requires every value of one attribute (column) of a relation (table) to exist as a value of another attribute in a different (or the same) relation (table). This is an extremely useful feature of DBMSs that helps to enforce the validity of your data.

    Here is one more example for you to practice with. The video below converts the student registration ERD created in the previous chapter in Access. See if you can create it without watching the video below (i.e. by looking at the ERD from the previous chapter). Then, watch this video if you get stuck or to verify your solution: