LookupTables

M

Matt

I have read in a few places to limit the number of lookup fields in my
DB. I am attempting to control the input into the DB and create a
valid values list for specific fields. As of now I have used the SQL
select statement to use the autonumber PK as the control source for the
combo box, but only show the second column. I can see where this will
lead to querying and relational difficulties down the road.

The key points are: How to control and limit input? Is there an easy
way to use a single valid values list? Would that even help?

any specific or general feedback would be great.. Thanks
 
A

Allen Browne

There is no problem with using a lookup table to hold the valid choices.
That's the normal approach, and any database I write has a few dozen of
those lookup tables.

There are problems with the Lookup wizard that is offered as a field type in
table design. You have probably read about those problems here:
http://www.mvps.org/access/lookupfields.htm

On any form, it makes sense to use a combo box for the user to select from
the available values. You set the RowSource property of the combo to the
name of the table that has the lookup values. If you want to hide the first
column and show the second, set these properties for the combo:
Column Count 2
Column Widths 0

However, there is no compulsion to use an AutoNumber as the primary key of
the lookup table. You can use a text field, and you don't have to worry
about hiding the column in your combo. This works very well for simple
lookups, such as choosing a category.
 
Top