normalisation

[Chris]

Hello group.

I have 3 Tables:

Objectives - ObjectiveID (PK)(AN) Objective (text)
tblObjectiveTasks - TaskID (PK)(AN) ObjectiveID (fk) Task (text)
tblEvidence - evidenceID(PK)(AN) TaskID (fk) Evidence(text)

An objective can have many tasks and a task can have many items of evidence.

Until now the tables have been set up for team members. Now Teams have
objectives and Managers have objectives too.

Should I Add a field into each table for the group or should I create a
seperate table to hold the information.

tblObjectives - ObjectiveID, Objective, Group
tblobjectiveTasks - TaskID, ObjectiveID, Task, Group
tblEvidence - evidenceID, TaskID, Evidence, Group

or

tblGroups - GroupID, ObjectiveID, TaskID, EvidenceID, Group.

 

[Chris]

Ignore this email. I only needed it in the ObjectiveID Group.

 

[Jeff Boyce]

Chris

What's the relationship? A team can have 1:m Objectives? Can more than one
team have the same Objective? If so, this is many-to-many, and requires two
more tables, both a tblTeam and a trelTeamObjective.

Can Tasks or Evidence belong to more than one Objective? If not, you'd only
need to connect an Objective to a Team. If they can belong to more than one
(and your current structure seems to say they cannot), you'd need to modify
your current structure to reflect the many-to-many relationship.