Knowledge Base Database

Im designing a database for information for my company(currently in Access). It will contain all the services thecompnay provides and the contacts for each service essentially a knowledge base. Its mainly to be used in the call centre to know where to place calls.

I have a Service table and a contact table.
Service table has serviceID, serviceName, Description, DivisionName as attributes
Contacts table has contactID,firstName,lastName, phoneNumber,jobTitle,emailAddress and a few others.

The problem I have is that there can be more than 1 contact for each service and each contact can be responsible for multiple services (ie I have a many-to-many relationship)

Can anyone suggest a structure for optimality that would allow me to search the database(using PHP) easily to find out all the contacts for each service?

Im guessing I need to create another table say ServiceContact containing the primary key, serviceID and contactID. Is that correct?

Unfortunately Im being asked to create this database now and not next semester when I actually do a DBMS course at uni. Its annoying but I have to live with it!

Thanks in advance

Jenna

i think at this moment when u r working in Access it would be best to make another table, as u have mentioned, ServiceContact which will map serviceID and contactID. This will solve ur many-to-many relationship problem.
lisa