Too Many Relationships?
I am building a datebase solution to track keys and I think I am doing somethis wrong. My current structure is:
As in each key belongs to one of a few groups (1st floor, 2nd floor etc.) Then each key has a name for the room it unlocks and then there are instances of each key.
To prevent duplicate data each database points to the database above it so for every record in KeyIndex it points to a record in KeyName and then KeyName points to record in KeyGroup.
The problem comes when I try to point to data for a key index but I am pointing to data several relationships away. Is there a way to store all of the data within KeyIndex but since data would exist multiple times have it change if I modified its parent? So if I have a KeyGroup field in KeyIndex, a lot of keys would have the same KeyGroup but if that changed in one location have it update accross all of the instances?