Help with Junction Tables

[sbart]

I can't seem to figure this out. I am self taught and doing a project for work. We are in the service repair industry. I have TblCustomers with Customer ID in it and TblTicketInfo with Ticket# in it(details about the ticket that gets filled out by the tech on site).
This is what I need junctions for:
Each customer can have multiple jobs on their account. Each job can have multiple Dispatch # on their account. Each Dispatch # results in one ticket #.

Any suggestions on how to do this?

[June7]

Sounds like Dispatch # and Ticket # are really the same thing.

Advise no spaces and special characters/punctuation (underscore is exception) in naming convention. Better would be DispatchNum or Dispatch_Num.

[orange]

See this free tutorial

[sbart]

I forgot about spaces and symbols Thanks. When someone calls in, service dept assigns a disbatch number. Then the field tech assigns a ticket number that they have onhand. I know I need junction table between customer and ticket info to get in the job #s, Disbatch #s and Ticket #s.

[ssanfu]

Each customer can have multiple jobs on their account. Each job can have multiple Dispatch # on their account. Each Dispatch # results in one ticket #.

Sounds to me like several one to many relationships.

1 customer can have many jobs and one job has one customer ==> 1 to many relationship

1 job can have many dispatch numbers and one dispatch number is for one job (account) ==> 1 to many relationship

1 dispatch number has one ticket number and one ticket number has one dispatch number ==> 1 to 1 relationship


Why do you think you need a junction table?

[June7]

Note correct spelling of dispatch.

Dispatches table has JobID as foreign key. Tickets table has DispatchID as foreign key. The link between customer and ticket is through dispatch through job.