I took a look at your test site and code, and have a theory:
The filter variables that are used to create the SELECT clause, such as statusCount__MMColParam2, are set from the corresponding QueryString variable by comparing it to an empty string - however, it looks like perhaps you intent is to indicate "any" with the first selection in the dropdown box, a dash "-" .
Then, in your select statement, in your AND clause you append a "%" wildcard, so I think the first portion of your WHERE clause would actually end up being
WHERE status like '-%' and campus like ...
Chances are, there is no matching row with a status that begins with a dash "-" ???
THe same theory holds for your "campus" filter; there, you don't have any wildcards, but again, is the dash supposed to mean "any campus" ?
Just a though, I don't know your assumptions and such...
In addition, I then see a third filter criteria included, derived from
statusCount__MMColParam4 = Request.QueryString("statusDate")
Not sure where this even comes from in the query string; it feels like it is unnecesary and mabye conflicting with the intended range of dates within which to search.
Generally, I would suggest that you debug this by printing out the final value of your assembled SELECT statement, once it's assigned to
I bet you'll find that if you compare that to the manual SQL query that returns data for you, it'll lead you down the right track.
Hope that helps,...