Too detailed DB? Need advice.

I'm making a database for a polling system and was unsure how to setup the database. I want to set it up so that the questions and options can be reused without replicating the intormation in the database. For example, the question "What is your favorite new movie?" and/or the option "Yes," if re-entered, will simply use the question/option already in the db. This is the table structure I came up with:

Questions:
QID
Question

Options:
OID
Options

Polls:
PID
QID
Date

Poll_Options:
POID
OID Results:
POID
Number

Now, my boss-man thinks that I possibly am taking it to far by making it so that the questions/options are not duplicated. He said it might be counter-productive, and might even be taken out to the point as to create SLOWER Queries.

Obviously, I'm no DB creating expert, so I'm looking for advice on what you think the best (speed wise, other wise) design would be. All comments welcome and very appreciated.

Johnny Allen Received on Thu Oct 19 2000 - 16:04:21 CEST