Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion GroupsFormsForms ProgrammingQueriesModules / DAO / VBAReports / PrintingMacrosDatabase DesignSecurityConversionImporting / LinkingSQL Server / ADPMultiuser / NetworkingReplicationSetup / ConfigurationDeveloper ToolkitsActiveX ControlsNew UsersGeneral 1General 2
Access DirectoryToolsTutorialsUser Groups
Related Topics
SQL ServerOther DB ProductsMS OfficeMore Topics ...

MS Access Forum / Database Design / November 2006

Tip: Looking for answers? Try searching our database.

Many To Many To Many

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Nanette - 27 Nov 2006 20:52 GMT
I have a Parts table, a Purchase Orders table, and a Purchase Requisitions
Table.
These are all many to many relationships and we will need to pull data from
all tables, such as PR's and Parts data, PR's and PO's data, PO's and Parts.

Is it possible to have one Linking Table that links three tables?

OR

Can I make a Linking Table between each table and have them all connected?
Kind of like a circular design?

OR

Should I just put linking tables between the Parts and Purchase Orders table
and another between the Parts and Purchase Requisition tables? But then how
do I get the connection between the Purchase Orders and Purchase Requisition
tables?

I'm going in circles, can anyone help!
Jeff L - 27 Nov 2006 21:57 GMT
I don't think you need the linking tables at all.  The parts table
layout, I'm assuming, is something like PartID, PartDescription.  Then
you use the Purchase Orders to purchase Parts.  This would be a
one-to-many relation.  Each Purchase Order would refer to one PartID.
I don't know what the difference is between a PO and a PR.  If I missed
something, let me know and maybe I can assist you further.

> I have a Parts table, a Purchase Orders table, and a Purchase Requisitions
> Table.
[quoted text clipped - 16 lines]
>
> I'm going in circles, can anyone help!
Nanette - 27 Nov 2006 22:56 GMT
Hi Jeff,

You are right about the Parts Table having a PartID and PartDescriptin.

A purchase requisition is a request to purchase goods and create a purchase
order. One step before getting a purchase order.

The original purchase requisition has many part numbers on it to order. When
the purchase requsition is okayed, then there may be two or more purchase
orders to order the parts (multiple vendors). Plus, some automated system is
creating a purchase requisitions for each part, so several purchase
requisitions are being assigned to one purchase order so the order can go to
one vendor.

A very strange system. What do you think?

> I don't think you need the linking tables at all.  The parts table
> layout, I'm assuming, is something like PartID, PartDescription.  Then
[quoted text clipped - 23 lines]
> >
> > I'm going in circles, can anyone help!
Jeff Boyce - 28 Nov 2006 00:46 GMT
Nanette

If your situation calls for a way to resolve many parts and many POs and
many PRs, yes, you can create a junction/resolver/relation table that pulls
in the IDs from all three of these tables.

Regards

Jeff Boyce
Microsoft Office/Access MVP

>I have a Parts table, a Purchase Orders table, and a Purchase Requisitions
> Table.
[quoted text clipped - 21 lines]
>
> I'm going in circles, can anyone help!
Nanette - 28 Nov 2006 01:03 GMT
Thanks Jeff,

That will make my life much easier!

> Nanette
>
[quoted text clipped - 32 lines]
> >
> > I'm going in circles, can anyone help!
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.