A combo can be from a table with only one field and use it bound.

--
Build a little, test a little.


"Barry A&P" wrote:

I am beginning to wonder if i overcomplicate my database. i am going to add a
field to my T_partnumbers for unit of measure (UOM) and can not decide if i
should do it like i have in the past and use a combo (on my forms of course)
with a row source to a T_UOM with Ea, LB, OZ, Ft Ect. and store the UOMid in
my part numbers table or just use a value list in my combo and save the
actual UOM abbreviation in my P/N table.

What is a good determining factor for which method to use?
And What to store in my table LB, OZ, EA, ect. or their respective ID's?

I feel linked tables for everything is becoming complicated as i view my
T_Partnumbers all of the data is Greek and meaningless unless i query and
join the appropriate tables, Maybe this is the Database method and i am
afraid to further stray from anything humanly recognizable..

Thank you for your thoughts..
Barry