I was thinking
OrderDetails (or something like that)
OrderDetailID
ItemID
VendorID
ItemSerial (I thought about this because each vendor might have the
same vendor, but different serial numbers, which I cannot put in the
items table)
Price
Purchased (y/n field)
Comments
I can then select all items and the vendors or a vendor and all the
items they sell. I really just need this simple thing. I don't need a
full-fledged inventory program. We don't need to track it like that.
It's more for initially purchasing. Sort of a furniture and fixtures
type database, but without the need for full asset management.
I thought that if I had just the two tables and put in say ItemID in
the Vendor table that I'd have duplicate rows. I'd have to type in the
vendor name each time.
Does this sound right? Thank you for any help.
-Ed
"jmDesktop" <needin...@gmail.com> wrote in message
news:1169478986.3...@s34g2000cwa.googlegroups.com...
Here's a grossly simplified design (you can add fields all you want).
Vendor(VendorID (PK), VendorName...)
VendorItem(VendorID (PK), ItemID (PK), Price)
Item(ItemID (PK), Description)
It's a classic Many-to-many. which means you need a junction table
(VendorItem) that links the Vendors to the specific items in the case
that one vendor sells many items, and may vendors may sell the same
item.
Vendor----(1,M)----VendorItem----(M,1)----Item
HTH,
Pieter