From the course: Access Essential Training (Office 365/Microsoft)
Join today to access over 22,600 courses taught by industry experts or purchase this course individually.
Primary and foreign keys
From the course: Access Essential Training (Office 365/Microsoft)
Primary and foreign keys
- [Adam] In a well-designed Access database you'll create many tables that relate back to records in other tables. If you have data that isn't specifically about the primary theme of the table, then it's probably the case that it should go into its own table. For instance, let's suppose that we wanted to store credit card information into our database. Here's a couple of questions that you might ask when determining where to store that credit card data. Does a credit card number describe our guests? And I'd say no, it doesn't. Will every guest want us to remember their credit card number? And I'd say probably not. Will some of our guests have multiple credit cards on file? That's probably a possibility. So, credit card numbers are not specifically about the guest, some customers won't have any and some customers will have many. All of these answers lead me to conclude that credit card information should be stored in its own table. So let's go ahead and create that credit card table…
Practice while you learn with exercise files
Download the files the instructor uses to teach the course. Follow along and learn by watching, listening and practicing.
Download courses and learn on the go
Watch courses on your mobile device without an internet connection. Download courses using your iOS or Android LinkedIn Learning app.