Job titles and job descriptions: it may be familiar!

[scubadiver]

I have been asked to design a database but I am not entirely sure how to go
about it.

I have job titles and job descriptions. A job title will have many job
descriptions and one job description can belong to many job titles.

There are 19 job titles and 330 job descriptions!!

The end product is a simple report which shows all the job descriptions for
a particular job title.

My initial idea would be to have a one-to-many relationship with the
descriptions being the "one" and the job titles being the "many".

Is it as simple as this, or will I need a "many-to-many" relationship?

 

[Duane Hookom]

Think of this like the Orders, Products, and OrderDetails in the Northwind
sample. Your Job Titles are like Orders and Descriptions are like Products.
An Order can contain many different Products like a Job Title can consist of
many different Job Descriptions. You need an "JobDetails" like the
OrderDetails that contains the JobTitleID (PK from JobTitles table) and
JobDescriptionID (PK from JobDescriptions table) fields.

 

[scubadiver]

From the perspective of a form, I would want to select the appropriate job
titles for each job description. I wouldn't want it the otherway round
because the database would be too cumbersome to use.

From your description I can see it would be two main tables with a junction
table (as a "m-2-m" relationship would do). What is the purpose of this type
of relationship and how would this work in a query? Is it as simple as
putting the fields of the two main tables into a query and being able to
produce the report that I need?

thanks

 

[Duane Hookom]

Apparently you would create a main single record view form based on the job
descriptions. Then create a continuous subform based on the junction table.
The subform would display a combo box with a row source of the Job Titles
table.

Creating reports would involve either a Record Source of all three tables or
a report/subreport similar to the form/subform.