N
Nick HK
I have a number of product codes like:
S7-xx07-yyzz........Type 1
S12-xx40-yyzz........Type 2
Both type 1 & 2 share 10 common properties. However, the properties
indicated by xx, yy & zz are derived from different sources
xx yy zz
e.g. Type 1 arch material arch design shade colour
Type 2 bulb colour shade type shade colour
The format of the product codes cannot be changed because they are
registered on a ream of certification documentation.
I'm accessing the data with VB/ADO, Implementing an Interface for each class
of product code, so each accessing the correct data is not a problem.
However, I would like to know the recommended way of dealing with this
situation. As far I see it, there are 3 options:
1. Single Product Code table, with fields "arch material" & "bulb colour
" to take care of the xx property (and similar for yy & zz). This leads to a
redundant field for each Product Code, but I have all Product Codes in the
same table, with all their other shared properties together.
2. Single Product Code table, with fields "xx" (linked to "arch material"
table & "bulb colour" table) , "yy" (linked to ..etc) & "zz" and a "Type"
field so I know what each entry means. This leads to all Product Codes in
the same table, with all their other shared properties together, but makes
it not easy to know what the values actually mean and integrity is out the
window.
3. Separate Product Code tables for Type1, Type2. This will ensure
integrity of each tables xx, yy, zz fields, but then I must duplicate the 10
common fields.
The situation is complicated by the fact that I actually have 4 types at the
moment.
Any advice would be greatly appreciated.
NickHK
S7-xx07-yyzz........Type 1
S12-xx40-yyzz........Type 2
Both type 1 & 2 share 10 common properties. However, the properties
indicated by xx, yy & zz are derived from different sources
xx yy zz
e.g. Type 1 arch material arch design shade colour
Type 2 bulb colour shade type shade colour
The format of the product codes cannot be changed because they are
registered on a ream of certification documentation.
I'm accessing the data with VB/ADO, Implementing an Interface for each class
of product code, so each accessing the correct data is not a problem.
However, I would like to know the recommended way of dealing with this
situation. As far I see it, there are 3 options:
1. Single Product Code table, with fields "arch material" & "bulb colour
" to take care of the xx property (and similar for yy & zz). This leads to a
redundant field for each Product Code, but I have all Product Codes in the
same table, with all their other shared properties together.
2. Single Product Code table, with fields "xx" (linked to "arch material"
table & "bulb colour" table) , "yy" (linked to ..etc) & "zz" and a "Type"
field so I know what each entry means. This leads to all Product Codes in
the same table, with all their other shared properties together, but makes
it not easy to know what the values actually mean and integrity is out the
window.
3. Separate Product Code tables for Type1, Type2. This will ensure
integrity of each tables xx, yy, zz fields, but then I must duplicate the 10
common fields.
The situation is complicated by the fact that I actually have 4 types at the
moment.
Any advice would be greatly appreciated.
NickHK