[AccessD] Mucking around

Simply put -yes.

Another question is "how to handle the populating and maintenance of these
lookup table's values"?

3 distinct variations come to mind:
1-a entry/edit form for each (typical but often redundant)
2-one entry edit form which is generic and filled via code depending on
which lookup table is chosen to have values entered/edited (saves form
layout time in the long run)
3-initially filling of tables with existing data - from there using the
NotInList event of forms to enter new values (works for simple lookups,
often requires DBA intervention depending on user trustworthiness(rare)
and/or security levels - often combined with either option 1 or 2)

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Mark A Matte

I meant if you had 30 completely different, not related drop downs...would
you create 30 lookup tables?
Example of dropdowns: State,Phone Type,Status,Name Prefix,ect...