Lookup tables - Yes or No

  • Thread starter Thread starter Reader1
  • Start date Start date
R

Reader1

I've heard a lot of debate about lookup tables.

Should I use them or not i.e. having separate tables with my choices listed
therein ?

Or should I use a drop down menu in the table i.e typing my choices directly
in ?

Or should I only use a form to input the different choices and not bother
with table look ups at all ?
 
Reader1 said:
Could you elaborate please ?

I'm a little confused still.
Click to expand...

A lookup field is where you build a table and in the design of the table you
choose ComboBox for the field's display and then specify that the ComboBox
should display data from a ValueList or from another table. This results in
a *table* datasheet that displays something other than what is actually
stored.

Since a table datasheet should never be used as an interface there is no
reason to do this and it can confuse people who later build a query with the
table and don't see the same data from that field in the query that they see
when they look at the table.

The act of using ComboBoxes and listBoxes on *forms* to display one thing
while storing another is perfectly acceptable and common practice. In those
situations the ComboBox or ListBox might be using a lookup *table* as its
RowSource.

So...
Lookup Fields = BAD Practice
Lookup Tables = GOOD Practice
 
Back
Top