Hello,
I am working on an issues database as a personal goal and I am attempting
to
understand the logic of table relation****p links. I've accomplished quite
a
bit of reading on this via various sources such as this forum, Access Help
and the Complete Access Reference book (maybe too many!) and I think I've
confused myself:
1. I have 7 tables established.
2. The primary table is: 'IssueDescription' and it has a primary key of
'Issue ID'.
3. I have made 'Issue ID' the foreign key in all of the other 6 tables
(each
table has its own primary key as well) and I, to ensure I have all tables
related, want to link the primary key to the foreign key in each table: a.
'IssueUpdate' (to do***ent comments and updates), b. 'IssueUserContact'
(to
do***ent individual who re****ted issue), c. 'IssueArea' (to do***ent the
area
where issue is occurring), d. 'IssueStatus' (to do***ent current status of
issue), e. 'IssuePriority' (to do***ent priority level of issue), f.
'IssueType' (to classify the type of issue).
***My primary question now is how to understand the logic of the
relation****p between the primary table and the other tables. For example,
I
see a '1-many' relation****p between the 'IssueDescription' table and the
'IssueUpdate' table because 1 issue can have many comments and updates. Am
I
thinking this through correctly?
But what about the other 5 tables?
For example, if I link the primary table 'Issue Description' to the 'Issue
Type' table (which currently has 3 different issue types, 'Informational',
'Error', 'Project'), would that be a 1 to 1 relation****p? I'm thinking
that a
single 'Issue' can only be categorized as one of the above choices,
correct?
Or should I be thinking that a single 'Issue' could possibly be one of
three
different issue TYPES and therefore a 1 to many relation****p?
Again, I'm just trying to understand the logic of how the tables should
relate via relation****ps. If you can provide some direction and advice on
how
to link the other 5 tables, I would appreciate it greatly.
--
jon
|
