• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 536
  • Last Modified:

how to create many to many relationship and report

Hello,
am attaching sample database-
am trying to understand how to make a many to many relationship with two tables.

have created the 2 tables-[tblItems] and [tblParts] and a 3rd table to make the junction.
but that is as far as I can get?

can a report be created with items with the same category number be listed and then right below have all the part numbers and the same category numbers below them?

Item descr qty      category  category number
Printer    51      HP          101
Scanner    65      HP          101
Monitor    84      HP          101


Printhead  15       HP         101
fuser      26       HP         101
etc....

thank you--
ManyToMany.accdb
0
davetough
Asked:
davetough
  • 8
  • 2
  • 2
  • +1
1 Solution
 
Rey Obrero (Capricorn1)Commented:
0
 
xtermieCommented:
You need an intermediate table just like you have done.
The two tables are joined 1 to many with the intermediate table so they are joined as many to many between them.  Uf you create the joins/relationships correctly, (same data type and size of the joined fields) access will then present the linked fields in the Datasheet view with the + sign as you describe.

For reports to be grouped, since you are using access, I would advise that you use the grouping levels available in the report wizard that will create several layers of grouping that can fit your needs (and sorting).

If you want to view in the way you mention, you can create a form (main table), subform (from a query or the other table) to view in a more organized manner.
0
 
Jeffrey CoachmanMIS LiasonCommented:
First, I see no reason why you need two tables.
I really can't see any real difference between a Part and an Item...?

You can simply add a "Type" field to one table (Item or Part)
ItemID
ItemDesc
Quant
Category
Type (Item or Part)
Category Number

Then what you are asking is ridiculously simple without the need for a Junction table
0
Free Tool: IP Lookup

Get more info about an IP address or domain name, such as organization, abuse contacts and geolocation.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

 
xtermieCommented:
I believe that the example is simple, but for sure if there are many parts for an item,  davetough is designing this right.
0
 
Jeffrey CoachmanMIS LiasonCommented:
This sample does exactly as you request without a junction table...
screenDatabase24.mdb
0
 
Jeffrey CoachmanMIS LiasonCommented:
Now, my feeling is that you could tweak the report to actually display the item "Type" in the group Header (and not have it repeat for every record (which is redundant), and possibly add summaries, ..etc, ...but again, ...my sample displays the data in the same way you specified.

JeffCoachman
0
 
Jeffrey CoachmanMIS LiasonCommented:
You can simply combine the tables by copying and pasting one table on top of the other in Excel (without the key fields)
Then add in your "Type" column and fill in the corresponding values
Then import this back into Access
Then simply add in an Autonumber field as the key...
0
 
Jeffrey CoachmanMIS LiasonCommented:
xtermie,

It can be designed in anyway the OP wants.
;-)
As you know, with many things in the database design world, there is no clear "right or wrong" design that will work for every situation.

My feeling was that I saw no real reason to create the junction table.
The fields in both tables are nearly identical, so it is not like the classic Many To Many relationship:
tblEmployees
tblProjects
tblEmpProjects (Linking table)
...In this classic Many to Many, the Employee table has no fields in common with the Projects table.

In the OP's case All of the fields are the same,
The only difference is the name of the PK field

This just sends out signals that perhaps this should be Normalized to bring all the items into one table.

Also, the current design will force the OP to create another new table for each, and any, new "Type"
So if there was a Parts table, and an Items table and a new "Modules" table, how would these three tables now be joined with a Junction table?

So again, I saw no real need for the Junction table and all of the associated complexity...

;-)

JeffCoachman
0
 
Jeffrey CoachmanMIS LiasonCommented:
...and I don't see any situations in the data where one "item" is associated with many "parts"
...or vice versa...
(A situation that Junction tables are created to deal with)

So again, I am not seeing a need for a Many to many table, but I am seeing reasons to combine the data into one table...

JeffCoachman
0
 
davetoughAuthor Commented:
Amazing how you made it that easy-thank you- so is many to many more for when you have different fields? thanks
0
 
Jeffrey CoachmanMIS LiasonCommented:
Having different fields can be one attribute of a many to many, but it is not a definition of a many to many.

A "Typical" many to many is when you have two tables and either on can have many of the other.
Examples:
Students/Classes
One student can be in many classes, and also, One class can have many students

Employees/Projects
One Employee can be in many Projects, and also, One Project can have many Employees

Doctor/Patients
...etc
These are examples of the most basic Many to Many.
They can become more complex if certain combinations can, or cannot, repeat.
If you research this on your own, you will encounter many names for this type of table:
Junction table
Association table
Intersection table
Many-To-Many table
Linking table
Mapping Table
Marry Table
;-)


In any event, ...
This did not seem to be the case in your design.

This is why in some cases you should not "tell" experts how to solve an issue.
   "I must create a many to many table"
...Because this forces us to think along those lines, possibly ignoring a better approach.

In most cases you only need to specify your ultimate need, and let experts suggest a design.

So instead, perhaps you should have just asked the same question, ...only leaving out the Many To Many "requirement"
For example:
Here is what I have...
Here is what I want...
What is the best design approach?

Make sense?

;-)

JeffCoachman
0
 
davetoughAuthor Commented:
yes- thanks for the help
0
 
Jeffrey CoachmanMIS LiasonCommented:
;-)
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Cloud Class® Course: CompTIA Healthcare IT Tech

This course will help prep you to earn the CompTIA Healthcare IT Technician certification showing that you have the knowledge and skills needed to succeed in installing, managing, and troubleshooting IT systems in medical and clinical settings.

  • 8
  • 2
  • 2
  • +1
Tackle projects and never again get stuck behind a technical roadblock.
Join Now