P
Parts Manager
Tables
---------------
tblItems: itemId (PK), & other item fields
tblVendors: vndId (PK), & other vendor fields
tblVitem: vitemId (PK), vitemReference (FK to itemId), vitemVendor (FK to
vndId)
I made the tblVitem by using the CTRL key and highlighting it's PK as well
as the new fields that are FK to their respective tables. I believe I read
it was called a Joined Table.
tblItems is a 1 to many to tblVitem, and tblVendors is a 1 to many to
tblvitem; butI am not sure a joined tblVitem is what I needed now.
What I need is way to have an item have many vendors, and a vendor to have
many items; for which I think is a many to many relationship with a Joined
Table.
1) Am I right in using a Joined table as I post above the correct way?
The reason I bring it up is that each vendor may have a different internal
Vendor Item Number for each item they sell. So I thought the primary key
for tblVitem would be a good place to hold that number while referencing the
Vendor for it and our internal item number of the part to purchase.
But when I view it the relationship window, it doesn't look right to me for
some reason. When I get some books it might make more sense, or I have it
wrong in the diagram.
The goal here is to have an item table with details about the item, a vendor
table with details about the vendor, and then relate these 2 in such a way
that any vendor may have any part and vice versa. This is where I am stuck
at.
I am placing an order for a couple of books today now that I have decided on
which books I want, but I would still like to understand the above while I
wait for the books to arrive.
Tim
---------------
tblItems: itemId (PK), & other item fields
tblVendors: vndId (PK), & other vendor fields
tblVitem: vitemId (PK), vitemReference (FK to itemId), vitemVendor (FK to
vndId)
I made the tblVitem by using the CTRL key and highlighting it's PK as well
as the new fields that are FK to their respective tables. I believe I read
it was called a Joined Table.
tblItems is a 1 to many to tblVitem, and tblVendors is a 1 to many to
tblvitem; butI am not sure a joined tblVitem is what I needed now.
What I need is way to have an item have many vendors, and a vendor to have
many items; for which I think is a many to many relationship with a Joined
Table.
1) Am I right in using a Joined table as I post above the correct way?
The reason I bring it up is that each vendor may have a different internal
Vendor Item Number for each item they sell. So I thought the primary key
for tblVitem would be a good place to hold that number while referencing the
Vendor for it and our internal item number of the part to purchase.
But when I view it the relationship window, it doesn't look right to me for
some reason. When I get some books it might make more sense, or I have it
wrong in the diagram.
The goal here is to have an item table with details about the item, a vendor
table with details about the vendor, and then relate these 2 in such a way
that any vendor may have any part and vice versa. This is where I am stuck
at.
I am placing an order for a couple of books today now that I have decided on
which books I want, but I would still like to understand the above while I
wait for the books to arrive.
Tim