I am in a structural dillema.
I have several one-many relationships, one side is a products table.
many side tables a barcodes, specifications, measurements, etc

The reason for having all these is that each has a different set of fields,
and each table is used for different

things. forms, reports, etc..

The catch here is that is a user wants to add another 'category', such as
recipes, he doesn't know in what table

to store the data. On the other hand, it is way to convenient for me to
perform label printing and check digit

calculations on the barcodes table, comparisons of measured values in
measurements etc.

The question is: Is it better to keep it that way and add another table for
user's "generic product information"

OR denormalize these tables and gather them up in one and use queries,
validation in forms and CAST (or any

other data type transformation) to perform the previously mentioned
actions??

PS. In the denormalizing scenario some fields will be truncuted to allow a
field to hold eg. barcode in one

record and product size in another.

Any help would be mostly appreciated.

Thanx in Advance.