Transaction Table

[Ecohouse]

I was discussing a project today and a question came up about using a
transaction table. I need to recreate an input form with many
different types of questions. The following is one type of question:

3) How would you characterize the racial/ethnic composition of the
individuals served by your program? What is the percent for each?

___American Indian or Alaskan Native
___Asian
___Black/African-American
___Hispanic or Latino

So what would be the best approach for this? Should I make a separate
table for this question? Should I keep all questions with percentages
for answers together in a table?

[salad]

Ecohouse wrote:

I was discussing a project today and a question came up about using a
transaction table. I need to recreate an input form with many
different types of questions. The following is one type of question:

3) How would you characterize the racial/ethnic composition of the
individuals served by your program? What is the percent for each?

___American Indian or Alaskan Native
___Asian
___Black/African-American
___Hispanic or Latino

So what would be the best approach for this? Should I make a separate
table for this question? Should I keep all questions with percentages
for answers together in a table?

You gave 1 type of question...a question that requires has multiple
answers with numeric input for a single question. How many questions to
you have? Are some multiple and some single inputs?

In this day and age of large diskspace, I wouldn't worry too much about
a table. You can have 255 fields. Were you planning on storing all
survey questions to 1 record or were you planning one record per survey
question?

[Ecohouse]

Thanks for the reply. For something like the question above I was
thinking of making a separate table with an identity key linking back
to the main table. There are a lot of questions like the one posted,
but there are also a lot of questions with yes/no or single answers.

I was just deciding the best way to go with this.

[salad]

Ecohouse wrote:

Thanks for the reply. For something like the question above I was
thinking of making a separate table with an identity key linking back
to the main table. There are a lot of questions like the one posted,
but there are also a lot of questions with yes/no or single answers.

I was just deciding the best way to go with this.

Whichever way is the easiest for you to code and the user to input.
Apply KISS.