A more long term solution would be to normalize your data. Assuming there is a person who has answered yes/no to each of these activities, what you have is a many to many relationship (one person can have many activities each activity can have many people who do it). Your structure should be:
People
ID
Name
Other personal Info
Activities
ID
Description
PeopleActivities
PeopleID
ActivityID
With your current structure, anytime you need to add a new activities (Basketweaving, Horseback Riding, etc.) you are going to have to change the table structure to include the new activity AND change all the queries to include the new field. With the normalized structure, you would just have to add a new record to the Activity table.
Leslie
Anything worth doing is a lot more difficult than it's worth - Unknown Induhvidual