Oh, so you're a big fan of implicit conversion? Try it with a multi-million (or more) row table. Why not save yourself the trouble and make the parameter type match...

You won't need the DISTINCT if you use a windowing function to remove the duplicates too.

Use the standard ROW_NUMBER() OVER (PARTITION BY <grouping columns> ORDER BY <columns>) AS rn
to assign each duplicate a row_number and then filter for  rn = 1.

Yep, sounds like a permissions issue.
Okay, found an article here that's even better than the one I originally posted...
Execute As article.

What are your rights in the database vs the person who can see everything? Sounds like you need a stored procedure with EXECUTE AS.

But don't take my word...

Couldn't you model it like this?

CREATE TABLE CallsFact (
     SurrogateCallKey INT IDENTITY
     , CallerID INT
     , CallType VARCHAR(8)
   ...

Did you read Jeff Moden's article on DelimitedSplit8K?

I used to work at a company that did healthcare data reporting.  I was stupefied when I found full names, birthdates and SSNs in the database. Went straight to the...

Remove the defaults. You need at least one that doesn't have a default value for SSRS to prompt you for values. Otherwise, the report will just run with the defaults....

You do realize that the data types for your parameters and the field types and sizes in the underlying table don't match, right?  If you want to pass multiple values...

Sounds like you need to put a rectangle on your report and then you can put the textboxes inside of it. That way, you can arrange them like you can...

Why not play with each one and decide for yourself? R support is already built into SQL Server.

I got the chunks apart... So I guess it's a place to start.  You need Jeff's string splitter function for this, which is here.  And here's my code......

Got Google?
http://sqljason.com/2010/12/subscripts-and-superscripts-in-ssrs.html