Perhaps it's just a matter of naming, then.
If your Products table holds one record for each product/item associated
with an Order, and will have as many rows (per Order) as the order has
products/items, then yes, your tblProducts and my trelOrderItem sound like
they match.
One way to get folks thinking more about this would be to describe the
actual structure of your tables. Here's an example of the ones I mentioned:
tblOrder
OrderID
OrderDate
SalemanID
...
tblItem
ItemID
ItemTitle
ItemDescription
UnitPrice
...
trelOrderItem
OrderItemID
OrderID
ItemID
Quantity
...
(an "OrderItem" table may also hold a "UnitPriceAtOrder", as a way of
ensuring that changes to the unit price in the Item table doesn't 'change
history')
Good luck!
Regards
Jeff Boyce
Microsoft Access MVP
--
Disclaimer: This author may have received products and services mentioned
in this post. Mention and/or description of a product or service herein
does not constitute endorsement thereof.
Any code or psuedocode included in this post is offered "as is", with no
guarantee as to suitability.
You can thank the FTC of the USA for making this disclaimer
possible/necessary.
Dave
A more traditional table design for orders/items would be:
tblOrder
tblItem
trelOrderItem
Your 'real-world' situation may be different, but the model you described
doesn't seem to allow for one order to consist of several items or one
item
to show up in several orders. That's a "many-to-many" relationship, and
that's what that third table handles...
Good luck!
Regards
Jeff Boyce
Microsoft Access MVP
--
Disclaimer: This author may have received products and services mentioned
in this post. Mention and/or description of a product or service herein
does not constitute endorsement thereof.
Any code or psuedocode included in this post is offered "as is", with no
guarantee as to suitability.
You can thank the FTC of the USA for making this disclaimer
possible/necessary.
- Show quoted text -
tblProducts will actually lookup values from a third table, so in
essence tblProducts is that intermediary table. Isn't it? Or is it?
Crap, now I've got to think.