LarryE
Active member
- Local time
- Today, 12:01
- Joined
- Aug 18, 2021
- Messages
- 908
And here's another design that can be just as effective. Instead of each child table holding a single foreign key from the parent table, we have one table that holds all the foreign keys. It's called a Junction table for obvious reasons. Data input can be faster using junction tables because you get to the point of creating input forms, the form for inputting data into the BackupFile table holds all 4 foreign keys so each foreign key would have a combo box for selecting the key and you can quickly move from one to another. I'll attach an example later for you to see.
And appending a 'FK' to the end of foreign key names as June7 suggested is a popular way to identify foreign keys in queries etc. ACCESS does not care, but it might be easier to keep track of foreign keys for you. So, the ComputerID field in the BackupFile table would be renamed ComputerIDFK or ComputerID_FK.
And appending a 'FK' to the end of foreign key names as June7 suggested is a popular way to identify foreign keys in queries etc. ACCESS does not care, but it might be easier to keep track of foreign keys for you. So, the ComputerID field in the BackupFile table would be renamed ComputerIDFK or ComputerID_FK.
