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

Typically the table you mention is called the OrderDetail table. Records in
the table are often referenced as LineItems.

a Customer  can make 1 or Many Orders
an Order can contain 1 or Many OrderDetails
an OrderDetail refers to a Product
a Product may refer to 1 or Many OrderDetails

In this set up an OrderDetail should reference the related Order (FK), the
product involved, the quantity of Product involved and the AgreedTo Price
per unit of Product involved.

There is a set of free videos on youtube that are often referenced.
Quality is so-so, but the message is good.
See https://www.youtube.com/playlist?list=PL196FE5448948D9B4

Good luck.

On Fri, Nov 28, 2014 at 7:51 PM, Bill Benson <bensonforums at gmail.com> wrote:

> 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
>