Advice on Table Setup

[jeffshex]

Just need some good info on this.

I am probably making it more tough on myself than I should but anyway...here goes.

I have a table where I list each job that a client got.
Of course there's a bunch more in that, but nothing to do with this.

Each Job can have a number of people assinged to it, yet I need to keep track of it all.

I thought of having a table with the jobs and having a field called JobID and then another table that links to it having JobID there as well (just not as a primary key).
That way I can have multiple JobID's for each person on the job.

That make sense?
If not just ask and I will clear up whatever I can.

Thanks!!!

 

[spizotfl]

so you have people and jobs. a person can work on many jobs and a job can have many people. you can use a table people on jobs or some such that has your personID and jobID in it to link the two.

 

[BobRodes]

The standard means of resolving a many-to-many relationship is to create an "associative" table that is in one-to-many relationship with each. Example would be a library database with books and patrons. The associative table would be loans. (Most associative tables don't have such nice real world names. Yours could maybe be called jobassignments.)

HTH

Bob