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.?

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

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!

Thanks again.
--
Thanks!

Dee


"John W. Vinson" wrote:

On Tue, 7 Aug 2007 15:00:02 -0700, dee wrote:

If the human beings responsible for input of the question number, etc. that
will be the PK make a mistake, it will be difficult to update.

If, however, an autonumber is used for the PK, then the change can be made
and cascading to all related tables.

You have it backwards.

Cascade Update is completely useless for an Autonumber, since an Autonumber
field cannot be edited. If instead you use a Text field as the PK, it *can* be
edited and cascade updates will take care of the related tables.

John W. Vinson [MVP]