Design Question: Lookup tables vs. Properties

[Lissa]

Hi Everyone -

I am taking over an former employee's database and I noticed he created lots of lookup tables that have only one value listed....

Is it more common to create a lookup table rather than just assign default values to create a small value list in the properties of a control?
I can see the point of creating a lookup table if there will be lots of values but for just one or two values, it just doesn't seem right.

What is the normal practice for handling lookups?

Thanks

 

[pbaldy]

Personally I generally use tables. I would only use a value list if I was really sure there would be no changes to the list over time. Putting the values in a table allows you to give the users a form to maintain the values.

 

[Pingo]

I think it's a matter of the frequency the default value changes. If it changes over time maybe I'll use it in a table and give the users the option to change it themselves. But if it changes only once a year, than I think it's a lot faster to just assign it as a default value in the table design, and change it as necessary.