>>If you're 100% sure that your design regarding these fields would not change, then you can put the fields into Member table and it will improve the performance. I'm not sure you will get a significant improvement, though.
>
>Well, if I want to locate members having one to x choices selected, where the members table would have two millions records, assuming that each member has at least two choices, it would make the one to many table with about 4 millions records. I would assume it would be much faster to simply SQL into the member table by searching on its field.

Yes, I think it would be faster.