Table design for Option button form

I don't think I quite understand your question, but here is a generic thing to keep in mind.

 

There have to be ABSOLUTELY NO RELATIONSHIP between how the data is stored and how it is represented on the screen. 

 

You can perform all the required transformation you need after it leaves the storage engine and before it reaches the UI.

 

While storing the data, all you worry about is integrity, normalization, performance, minimum storage, accommodating future enhancements, etc.

Hi Niilesh,

 

 

Thanks for the answer.

 

but with the same table structure if we want to bind this table data to view in MVC then to bind this we have to add condition on every textbox.

 

how we can do that then?