alternative to lookup fields

[AdmSteck]

I was looking through this newsgroup today and came across this website that
listed the "10 Commandments of Access":
http://www.mvps.org/access/tencommandments.htm
My question is about the second commandment, which proclaims lookup fields
as the creation of "the evil one". What alternatives are there if you need
to create a field that users can be able to add values? Thanks

 

[Rick Brandt]

I was looking through this newsgroup today and came across this website that
listed the "10 Commandments of Access":
http://www.mvps.org/access/tencommandments.htm
My question is about the second commandment, which proclaims lookup fields
as the creation of "the evil one". What alternatives are there if you need
to create a field that users can be able to add values? Thanks

You still use a lookup *table* and then create a form with a ComboBox that
the user can choose selections from for data entry. One should never use
the tables directly as a user interface and that is the only time a lookup
field defined in the table is useful.

 

[Joan Wild]

I was looking through this newsgroup today and came across this
website that listed the "10 Commandments of Access":
http://www.mvps.org/access/tencommandments.htm
My question is about the second commandment, which proclaims lookup
fields as the creation of "the evil one". What alternatives are
there if you need to create a field that users can be able to add
values? Thanks

Creating a field where users can add values really has nothing to do with
lookup fields. The issue is with using/creating the lookup wizard in a
table. There is nothing wrong with having lookup tables, where information
is looked up for ease of data entry.

Create the lookup on your forms instead, by creating combo boxes that lookup
values in another table.

Creating a lookup field in a table just causes confusion (what you see is
not what is stored); it creates unnecessary extra indexes and relationships.