The correct way to do it is to break your single table into two separate tables.
One would be the member master, and have the member ID and stuff like name, gender (items which the member hopefully only has one of).
The second table would have a key that contains two fields, the member ID and probably an autonumber field ("specialty_id" or some such name), and then a field for the specialization code. You can then have any number (zero to way more than you need...) of specializations per member.
Join the two tables together, using the member ID, and you can easily get the query results you are looking for.
This whole process is called data normalization, and there have been many books written on it. It's not an "easy" answer, but its the way professional system designers work.