What is the correct database design for a "How did you hear about us?" with a customizable "Other" option?

I have a relational database with a user table in it.

I have a website with a "How did you hear about us?" dropdown list.

The dropdown list is table driven. The table used to populate the dropdown has options like "Station 1", "Station 2", etc. One of the options in the drop down is "Other".

When the user selects "Other" a textbox appears so they can input their custom answer. The user then clicks save and the selected option is stored in the database.

Herein lies the problem. What would the ideal normalized table structure look like for storing the selected option when the selected option is "other" and contains extra data. I can think of several ways to do structure it but none of them seem "clean" to me.

One option would be to add a column to the user table and store the text value there but this isn't normalized.
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Guy Hengel [angelIII / a3]Billing EngineerCommented:
you have the table of the possible selectable options, like this:
0     Other           99
1     Station 1      1
2     Station 2      2
... etc ..

and for the customer's settings:
1                             1                 <NULL>
2                             0                 blablah ...

note that you may want to save some user comments also for the other options

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
trueguruAuthor Commented:
Yes I thought about this. Definitely you want the ID from the "WhereDidYouHearAboutUs" table but it doesn't seem correct to store the extra "Other" field data in the user table.

I don't believe that there is a more "elegant" solution so, unless someone else comes up with an alternative, I'm going to accept your solution and continue coding.

Thank you!
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.