Scott Klarenbach wrote:
These are the tables in question:
RFQ (Request for Quote)
Part
Inventory
Inventory items ALWAYS have a partID.
RFQ items ALWAYS have a partID.
However, sometimes, RFQ items have an inventoryID as well. Now, we have a
redundancy problem. Because, in those instances w
Scott,
>I'm sure this type of problem is run up against all the time, and I'm
>wondering what the best practice methodology is from experienced DBA's.
It looks like the kind of problem database schemas are meant to
_avoid_.
>From your description it seems you have ...
part (
partID PRIM
These are the tables in question:
RFQ (Request for Quote)
Part
Inventory
Inventory items ALWAYS have a partID.
RFQ items ALWAYS have a partID.
However, sometimes, RFQ items have an inventoryID as well. Now, we have a
redundancy problem. Because, in those instances when the RFQ has an
invento
