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
|
|||
|
|||
"Lookup" field choices
Hi,
I am creating a field the states the relationship of a survey respondent in relation to the head of the household. These are coded - 1 = spouse, 2=son, 3= daughter, etc. There are about 15 different options and one of these options must be selected. Should I create a separate table, or should I create a lookup where I input the choices? Any advice on the best approach? Thanks! -- Thanks! Dee |
#2
|
|||
|
|||
"Lookup" field choices
Create a separate table; easier to maintain.
Also, avoid the 'lookup field wizard' in a table, as it will just cause you grief. Instead create lookups on your forms to lookup the values in your table. See www.mvps.org/access/lookupfields.htm -- Joan Wild Microsoft Access MVP "dee" wrote in message ... Hi, I am creating a field the states the relationship of a survey respondent in relation to the head of the household. These are coded - 1 = spouse, 2=son, 3= daughter, etc. There are about 15 different options and one of these options must be selected. Should I create a separate table, or should I create a lookup where I input the choices? Any advice on the best approach? Thanks! -- Thanks! Dee |
#3
|
|||
|
|||
"Lookup" field choices
Hi Joan,
Thanks for your response. I'm actually now wondering if I should just add it in my answers table. I am creating a survey database - so I have tables that contain questions, answers and responses. I was directed to Duane Hookom's survey database which put me on the right track. There can be often 4 or 5 answers that respondents can choose from for each question. This would simply be 15 or 20 choices as opposed to 4 or 5. Does that make sense to you? Thanks! -- Thanks! Dee "Joan Wild" wrote: Create a separate table; easier to maintain. Also, avoid the 'lookup field wizard' in a table, as it will just cause you grief. Instead create lookups on your forms to lookup the values in your table. See www.mvps.org/access/lookupfields.htm -- Joan Wild Microsoft Access MVP "dee" wrote in message ... Hi, I am creating a field the states the relationship of a survey respondent in relation to the head of the household. These are coded - 1 = spouse, 2=son, 3= daughter, etc. There are about 15 different options and one of these options must be selected. Should I create a separate table, or should I create a lookup where I input the choices? Any advice on the best approach? Thanks! -- Thanks! Dee |
#4
|
|||
|
|||
"Lookup" field choices
I still think you should make a separate table for this. If/when you need to edit/add to the list, you only need to add/edit the records in the table (one place). If you use a value list, then you need to make the changes in design view of every form where it is used.
It's much easier to make the change in one place; and it is easier for users as well. The fact is that this is data, and that belongs in a table, not in some value list hidden in a table's design. -- Joan Wild Microsoft Access MVP "dee" wrote in message ... Hi Joan, Thanks for your response. I'm actually now wondering if I should just add it in my answers table. I am creating a survey database - so I have tables that contain questions, answers and responses. I was directed to Duane Hookom's survey database which put me on the right track. There can be often 4 or 5 answers that respondents can choose from for each question. This would simply be 15 or 20 choices as opposed to 4 or 5. Does that make sense to you? Thanks! -- Thanks! Dee "Joan Wild" wrote: Create a separate table; easier to maintain. Also, avoid the 'lookup field wizard' in a table, as it will just cause you grief. Instead create lookups on your forms to lookup the values in your table. See www.mvps.org/access/lookupfields.htm -- Joan Wild Microsoft Access MVP "dee" wrote in message ... Hi, I am creating a field the states the relationship of a survey respondent in relation to the head of the household. These are coded - 1 = spouse, 2=son, 3= daughter, etc. There are about 15 different options and one of these options must be selected. Should I create a separate table, or should I create a lookup where I input the choices? Any advice on the best approach? Thanks! -- Thanks! Dee |
Thread Tools | |
Display Modes | |
|
|