I am trying to deploy a CR application. I have several embedded reports and am using the ReportDocument model and runtime parameters. When the report loads, I pass in the login information used in other parts of the application. The login info (username, password, db server and db name) is all correct, however, the reports seem to be using cached login information that was used when the reports were designed - different username, password, etc. Even though the application can set those values and even though I call the update login info function, the reports still try to use the information that was cached during design time.

Why is this happening and how can I go around it? I assume that because I am using embedded reports some of that might be cached in a dll or something, but I am not sure.
Does anyone have any ideas or suggestions on how to isolate the problem and/or fix it?

As always, any comments and suggestions are greatly appreciated.

Actually, the weird part is that it keeps the old server name, but not database name, keeps username, but not password. However, the database name textbox on the CR login form is disabled, and the password one is not. But of course w/o the db name, it's no good.
The puzzle here for me is that the code works fine from within VS2005, but when I build the installer, which contains CR runtime, I get that bug. So I am not even sure how to debug that. I am not sure what in the installer process I could have messed up, but this kind of an error is most definitely something I would have never expected and I don't know how to approach it. I will try a few different things in the code tomorrow, and then go through the installer build process again and see what happens.
If you have suggestions on what  to try or look for, please let me know.