I have a database that needs to store the availability of the volunteers for a non profit organization. I was looking at using 2 tables, one holding the choice of yes/no and then joining it multiple times to a table storing the answers in fields based on the day and am/pm. so the table would have a field for each part of a day, eg. SundayAM, SundayPM, MondayAM... etc.
I get the feeling that could be come a mess. I don't want to use yes/no datatypes so the Choice field in the Choices table are strings Yes and No, the availability table just stores the ID of the 2 choices in the choice table. So the SundayAM field would store either a 1 or 2. See this for why I am not using Yes/No field types.
So I was thinking if I had a field that stored a string like "SunAMNPMN,MonAMYPMN,TueAMYPMN,WedAMYPMN,ThuAMYPMY,FriAMNPMY,SatAMYPMY" I could parse it and figure out how to enter and show it on a form through some code. That example is one of 28 (I think) possibilities. Then I could just store that in the Volunteer data table. But I am hoping someone has a better simpler solution than either of my ideas.