Table design where a field isn't always completed

[Will]

Hi
I have a table which stores product information called tblProducts. I need
to add a field ProductWeight to this table but not all products have
weights. My question is should I add this field to tblProducts and have
records which have blank fields for weight or should I create a new table
e.g. tblProductWeight with the fields ProductID and ProductWeight containing
only products where weight is recorded? What are the
advantages/disadvantages of each method?

Thanks

Will

 

[Rick B]

Most tables will have some fields that are blank. For example, "spouse
name" would be blank for single folks. "termination date" would be blank
for employees who are still working.

I would think that if most of your records will have a value, you would want
to keep the field part of your table.

Rick B