Hi again, John,

When you adapted his database, did you do so from scratch or modify what was
there? I have a few areas that I'm not sure of and don't know if you could
provide some guidance:

1. He has all of his answers in the answers table, listed by question
number and response, i.e. 1. first choice answer 1. second choice
answer 1. third choice answer, etc. I have some about 3 questions that
require a choice from about 15 - 25 choices. Should I simply continue his
way of doing this, or create sub-tables?

2. On my forms, I have the respondent code and the interviewer code, plus
the date and time the survey was filled in. I decided to use the question
code as my PK because it is unique - each has its own combination of letters
and numbers - however, these other fields aren't numbered. Should I add a
fictitious number and have the interviewer code, date, etc. as just another
answer, or should I treat these differently?

3. I also have a lot of information about the respondents in a separate
table, but I guess this is just additional information that I would add to
the one in Duane's db.

4. I have two sets of surveys - one for adults and one for children - the
names of the surveys indicate which is which. I suppose there is no need to
separate these at all... Just have a table with questions, a table with
answers, a table with responses.

Sound correct?

Thanks!

--
Thanks!

Dee


"John W. Vinson" wrote:

On Tue, 7 Aug 2007 16:32:02 -0700, dee wrote:

Hi John,

I value your advice, help and input. I will use the text fields that make
sense. I know that there is a possibility of human error when inputting.
Any suggestions on how to handle that? I guess just the validation rules,
field size, etc.?

Well, to the extent that you want the user to select from a set of existing
values (question numbers say), use the builtin tools that do so: Combo Boxes
and Listboxes. It's much easier to make an error typing blindly into a blank
textbox than selecting from a list.


Perhaps part of the process will be having the data entry verified after
input.

The Form's BeforeUpdate event is the place to do so. You can check for valid
values and combinations of values on the form, and set Cancel to True with a
warning to the user if there are errors.

I believe you had also guided me recently to the survey database by Duane
Hookom. Thanks so much. It has helped to a degree, except that the audience
is really those who wish to just modify the questions and survey titles, etc.

I am trying to create my database from scratch. Quite a challenge. If you
have any other resources or suggestions regarding this type of database, I'd
really appreciate hearing about them!

I've *adapted* Duane's At Your Survey a couple of times to meet different
needs. It's hard to top.

John W. Vinson [MVP]