My SQL isn't great, but it should be possible to do this with just one query - which obviously reduces the load on your database*. And involves less typing
If I'm right, that should return a recordset of two columns; the first is a list of everybody's Member ID, the second... well, it'll be their Member ID if they're in SurveyDisqualifiedMembers, or NULL if they're not. Depending on what database you're using, there are various ways of making it return something a bit more useful than NULL, or you can just deal with it in the ASP.
sSQL = "SELECT DISTINCT Members.MemberID, SurveyDisqualifiedMembers.MemberID AS DisqMember FROM Members LEFT JOIN SurveyDisqualifiedMembers ON SurveyDisqualifiedMembers.MemberID = Members.MemberID"
Set objRS = gobjConn.Execute(sSQL)
* In any case, looping through recordsets is Bad. It chews up processor resources. Even if you do stick to looping through one result set, firing off SQL queries each time, have a look into using objRS.getRows() to get your initial data into a more manageable array.