Slightly different structure Mark.
I have a Departments Table. It lists both the Team names and our internal departments. I do not explicitly have the Teams in a separate table. There is a column in this table that identifies each record as either a department or a team, but they are housed in one place.
But I think I follow the logic and can apply it to be the same method. Only question is if multiple people are logged into the system at one time wont there be multiple #1's in the table? Or is it pulling somehow locally on each users machine?
And also my tasks are not connected to my Departments table. The Tasks are related to the team members table.
So the structure goes:
- A department has many team members (This relationship is called Related Department)
- A department has many team members (This relationship is called Related Teams)
- A team member has many tasks.
The department table has both internal departments as well as Teams so it has two relationships.
Does that make sense? perhaps that was built wrong and I need to split off departments and teams, but it still doesnt flow down to tasks. Unless I make another relationship that is automatically set based on who is assigned to the task.
------------------------------
Ivan Weiss
------------------------------
