If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
alternative to lookup fields
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 |
#2
|
|||
|
|||
alternative to lookup fields
"AdmSteck" wrote in message
... 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. -- I don't check the Email account attached to this message. Send instead to... RBrandt at Hunter dot com |
#3
|
|||
|
|||
alternative to lookup fields
AdmSteck wrote:
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. -- Joan Wild Microsoft Access MVP |
Thread Tools | |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Lookup fields | Luis Miguel | Database Design | 7 | June 21st, 2004 02:54 AM |
Lookup fields on label report | Howard | Setting Up & Running Reports | 1 | June 3rd, 2004 02:43 AM |
Lookup fields - what's wrong with them? | NATHAN SANDERS | New Users | 2 | May 4th, 2004 10:51 AM |