Your plan included that the Student SSN field would cross$-$reference to the Events table, since each student's SSN is a unique number.

Everything is running smoothly during the setup, until during one of your weekly project meetings your boss reminds you that they cannot collect students' social security numbers because of privacy and identity theft concerns. You ask the developer to hold up with further design until you cari find a solution.

After researching the problem online, you decide to ask the developer to create a new Student ID field that can be unique to each student and referenced in the Events table. This seems to work well, but now you are over a week behind schedule.

The next week, you get an email from the web developer asking where you would like to store the database once it is ready.