Many to Many Relationship
Hello All, I have a table with lists of tasks that we need to work on daily and another Schedule table that has all employees and their availability dates. The usual situation is that 1 employee can ...
Forum Discussion
Before you go any further I would look at that key field. I do not think the date is going to be unique for an identifier. If you have two sets of scheduled tasks on the same day it is going to create an issue with that key field.
It sounds like you need a task assignment table which is a many to many (join) relationship between your tasks and your assignees (whatever you are calling them, maybe resources or employees, etc.)
That allows the multiple assignments.
I personally, in most business cases, do not like multiple assignees in tasks as it could lead to "I thought the other person had it" But that is just me and some people on my team dont like that. But since I develop QB for our team I get the last say :)
------------------------------
Ivan Weiss
------------------------------
It sounds like you need a task assignment table which is a many to many (join) relationship between your tasks and your assignees (whatever you are calling them, maybe resources or employees, etc.)
That allows the multiple assignments.
I personally, in most business cases, do not like multiple assignees in tasks as it could lead to "I thought the other person had it" But that is just me and some people on my team dont like that. But since I develop QB for our team I get the last say :)
------------------------------
Ivan Weiss
------------------------------
- Hi Ivan, I already have that as shown in the diagram it's called "Schedule" table, it has a many to one relationship to "Employees"
------------------------------
Karim Gawish
------------------------------- I am not quite understanding exactly what you are trying to achieve with the schedule table. What is that table doing for you? Why not just have the tasks and employees tables with a join table in the middle? That in essence would be your schedule table but the arrow to employees flipped the other way. I am not following the use case of that schedule table.
------------------------------
Ivan Weiss
------------------------------
