Evil of lookup tables?

[Johnny]

I have read this admonition against using lookups in tables but frankly it confuses me.

I have a list of 2 hour blocks in their own table because I want to control what is specifically selected when someone wants to add these time blocks in. The table has two columns, the hourdescriptor and the hourID (autonumber).

I refer to this table in a lookup operation to display these specific hour blocks in another table.

Is that what I am NOT supposed to do? If so how do I control what I want displayed in the dropdown in a "approved' way and be able to use that value later on?

 

[pbaldy]

Lookup tables are fine and normal and part of a well-designed database. What many of us don't like are lookup fields in tables:

http://www.mvps.org/access/lookupfields.htm

 

[Johnny]

Okay so sounds like I did it right. But when I try to fill a textbox with the value of the combobox it keeps just showing me the HourID (primary key) value not the descriptor value!

When I use the builder it lets me enter the lookup table field but when I change to form view shows me the row ID value.

edit: Nevermind I see I have to specify a column, duh.

 

[pbaldy]

Glad you got it sorted out.

 

[Simon_MT]

You can also see the descriptor and use the ID you can set the ID field to "0" lenght with the combi-box.

Simon

 

[Johnny]

Thank you both for your time and help.

John