After using Microsoft's SQL Server Reporting Services for a day or so I realized that there is no easy way to pass in multiple values for a parameter to the service and have it return the results. For instance, if I want to return a report where the variable is equal to 33, 34, and 35 there is no easy way to do it.

I use these multiple values in my SQL query to narrow my results using an Where variable IN(33,34,35) type of clause in my SQL statement.

Looking at the documentation I did run across a property called ReportParameter.MultiValue Property, which is a boolean and always set to false. So that's not useful at all.

/sarcasm
I guess I can understand why MS didn't include this obviously advanced feature. It would require them to write a very intense parameter parsing function and that would probably add at least 50 years onto the product development time.
/sarcasm

Now I apparently have to write my own user defined function for the Reporting SQL server and then use that in my script that defines the Dataset.We'll see how that goes.

So basically, instead of spending time focusing on the problem I have to focus on a weakness in the tool. This is like a carpenter trying to figure out how to use duct tape to get his hammer working properly instead of building a house. This pisses me off. I spend more time working around tools then using them to create something useful. If developers could get some decent tools we might be able to actually give the user's what they need.