design help

I want to keep track of products , its inventory and any faults to the
products.. Can someone provide a broad design for this ? As far as table
names and their relationship to other tables. Doesnt have to be detailed and
does not have to include data types,etc.. ThanksIt really depends on what you want to do, how much data your need to =
capture, and how you want to use the data. =20
It would seem that these are the bare minimum:
Product table
ProductID
ProductName varchar
Inventory table
InventoryID
ProductID
LogDate
InventoryQty
Defect table
ProductID
LogDate
DefectCode
Explanation
--=20
Keith
"Hassan" <fatima_ja@.hotmail.com> wrote in message =
news:uwfz3XkJEHA.3120@.TK2MSFTNGP11.phx.gbl...
> I want to keep track of products , its inventory and any faults to the
> products.. Can someone provide a broad design for this ? As far as =
table
> names and their relationship to other tables. Doesnt have to be =
detailed and
> does not have to include data types,etc.. Thanks
>=20
>|||Does that mean the relation between product and inventory or product and
defect might be a one to one relation
"Keith Kratochvil" <sqlguy.back2u@.comcast.net> wrote in message
news:ugJKpikJEHA.2660@.TK2MSFTNGP09.phx.gbl...
It really depends on what you want to do, how much data your need to
capture, and how you want to use the data.
It would seem that these are the bare minimum:
Product table
ProductID
ProductName varchar
Inventory table
InventoryID
ProductID
LogDate
InventoryQty
Defect table
ProductID
LogDate
DefectCode
Explanation
Keith
"Hassan" <fatima_ja@.hotmail.com> wrote in message
news:uwfz3XkJEHA.3120@.TK2MSFTNGP11.phx.gbl...
> I want to keep track of products , its inventory and any faults to the
> products.. Can someone provide a broad design for this ? As far as table
> names and their relationship to other tables. Doesnt have to be detailed
and
> does not have to include data types,etc.. Thanks
>|||Yes, product and inventory would be related on ProductID. Since there =
could be multiple inventory checks per day the other PK column could be =
InventoryID OR LogDate could be be part of the PK.
Within the Defect table I am thinking that LogDate and ProductID would =
make up the PK. Then again, LogDate could simply be part of the table =
and another column (identity, for example) could be added the PK. =20
There is not a right or wrong way to do it...you just have to pick a =
method that works for you and meets your business requirements.
--=20
Keith
"Hassan" <fatima_ja@.hotmail.com> wrote in message =
news:uTiZuDlJEHA.3944@.tk2msftngp13.phx.gbl...
> Does that mean the relation between product and inventory or product =
and
> defect might be a one to one relation
>=20
> "Keith Kratochvil" <sqlguy.back2u@.comcast.net> wrote in message
> news:ugJKpikJEHA.2660@.TK2MSFTNGP09.phx.gbl...
> It really depends on what you want to do, how much data your need to
> capture, and how you want to use the data.
>=20
> It would seem that these are the bare minimum:
> Product table
> ProductID
> ProductName varchar
>=20
> Inventory table
> InventoryID
> ProductID
> LogDate
> InventoryQty
>=20
> Defect table
> ProductID
> LogDate
> DefectCode
> Explanation
>=20
>=20
> --=20
> Keith
>=20
>=20
> "Hassan" <fatima_ja@.hotmail.com> wrote in message
> news:uwfz3XkJEHA.3120@.TK2MSFTNGP11.phx.gbl...
the[vbcol=seagreen]
table[vbcol=seagreen]
detailed[vbcol=seagreen]
> and
>=20
>