Dynamic Connection String with Stored Procedure

Has anyone been able to find a way to use a stored procedure with a dynamic connection string?

Do you mean you want to use different connection strings with the same report i.e. different datasources?|||Yes and no. Same report, same data source, different connection strings for different people. We have been able to do this up until we hit the reporting services bug. Others on this message board have had the same problem. You get the connection string to work but every time you run the report the Command Type keeps reverting back to text instead of stored procedure so the report errors out. Others on this message board have said that they ripped the code out of the procedures and embedded it in every report because they haven't been able to get around the bug. Just checking if anyone ever got around it as we really don't want to have to do this.|||Whenever you click on view code this portion is missing after the query element, this is why it keeps erroring out and the dataset keeps reverting back to text. This is a BUG.

<CommandType>StoredProcedure</CommandType>

When we add it in the code window, the report will now run and function as it should as long as you don't click on the data tab again. If you click on the data tab again you will have to go back in and add this code in again because it will be gone.