Task app data normalization

[rajivvaishnav]

Hey

I am building a task app and here are my tables :

Client table :

Task Table :

Task_ref table which has all the master task which is common for all the employees and clients :

Here is employees table :

Here is the job table :

Here is the jobid table which has just job id which gets copied to task table

Everything is working fine but issue is when i create a job, here is what I do :

I select the employee to whom I want to assign the job, then i select the task from enum list populated from task_ref table, then I select the client and when i save, it creates 10 records for (10 fixed tasks in task_ref), so for each employee it creates 10 records in task table for each client, so my question is, is this a good way? becuase I see lots of rows created in task even if i just add 2 clients and asign them to 2 employees, I hope this makes sense, am I wrong somewhere ?

can someone help me to re-structure my tables.

Best Regards

Rajiv

[TeeSee1]

if one Job, which has a client and an employee associated with it, has 10 tasks (Task table is a child table of the Job table) then, yes, it is correct to have 10 rows in the Task table per job.