Hi All,
My question is more to get a second opinion (or two or three..). I'm constructing a complete database for my company. I have developed forms and tables for collecting products and constructing product codes. So basically i have a table of all the products and a table of all the materials used to make those products (its a little more complicated than that of course). Now I wish to make a form/table so that the user can list all the material and quantities that go into making a product.
My question is what is the most efficient way of doing this? So far I have thought of two options, my first was to have a record for every product with a single field holding all the materials together, however there can be up to 30-40 materials per product, and i've read this method isn't the best. My other option was to have a record for every product/material join in a many-many table, does this seem like im complicating it too much. Of course the table storing this data is in the background but it could grow to 30,000 records using this method. Thanks in advance for your input.
Regards,
Mike
My question is more to get a second opinion (or two or three..). I'm constructing a complete database for my company. I have developed forms and tables for collecting products and constructing product codes. So basically i have a table of all the products and a table of all the materials used to make those products (its a little more complicated than that of course). Now I wish to make a form/table so that the user can list all the material and quantities that go into making a product.
My question is what is the most efficient way of doing this? So far I have thought of two options, my first was to have a record for every product with a single field holding all the materials together, however there can be up to 30-40 materials per product, and i've read this method isn't the best. My other option was to have a record for every product/material join in a many-many table, does this seem like im complicating it too much. Of course the table storing this data is in the background but it could grow to 30,000 records using this method. Thanks in advance for your input.
Regards,
Mike