I don't like value lists either. Opinions vary, but it is just as easy to
store these values in a table. Then you can give your users a form in which
they can maintain their own dropdown lists. If they do not have this
option, they must come to me as the programmer to add it, because the
information is stored in the APPLICATION rather than in the DATABASE.
Personally, I think (and EF Codd agrees) that all data should be stored in
the database and not in the application.

--
--Roger Carlson
Access Database Samples: www.rogersaccesslibrary.com
Want answers to your Access questions in your Email?
Free subscription:
http://peach.ease.lsoft.com/scripts/...UBED1=ACCESS-L

"el zorro" wrote in message
...
SO I've read a little thing that warns against using the
LOOKUP feature when designing tables. Apparently its not
good to assign values to a field based on values in
another table; better to just join the tables in a query
and get your values that way.

But what about using the VALUE LIST lookup option when
designing a table? This does not reference another table,
but you just type in the list of values from which you
want the user to select. For example, I might want to
limit data for a Status field to "Approved," "Pending."
and "Denied." SO rather than creating a separate table
for these 3 entries, I just type them in to the table
design, via the LOOKUP feature. Any harm in that?
(Thanks!)