[AccessD] Confused by One to Many versus One to One

I guess you're allowing many products to be ordered on one order, with consequentially many entries in the OrderProduct
table corresponding to the one in the Order table.

Is this helping to answer your question?

John


-----Original Message-----
From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Bill Benson
Sent: 29 November 2014 00:52
To: 'Access Developers discussion and problem solving'
Subject: [AccessD] Confused by One to Many versus One to One


I almost never make relationships one to one, and yet my databases always seem to "work." By work, I mean that I never
seem to run into situations where I cannot accomplish what I want to, in terms of record insertion, queries, etc. So I
now have a situation where maybe that is not a good idea.

 

I have Order and Product tables, one order can contain many products. So I required an OrderProducts table to distribute
the same OrderID across numerous ProductIDs.

 

My question is, should the relationship between the Order and OrderProduct, on the OrderID and FKOrderID, be 1-to-1, or
1-to-many?

 

Likewise, the same question for the OrderProduct and the Product, on the ProductID and the FKProductID?

 

 

-- 
AccessD mailing list
AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com