Crystal Report generating data from incorrect data source

Question

In dealing with a recent post about an upgrade to Crystal XI R2 mixing badly with an old VS 2003 project ( Update to CR XI R2 and service pack 4 issues with VS 2003 ), I've been attempting a few things to get past the issues with missing parameters and so on.  I found that I actually was using a parameter in the report I was trying to run, so I assigned the proper value to said parameter, ran the report, and lo and behold all was well.  The data was coming back correctly, no errors, everything seemed fine.<br><br>
Then I checked the results against the production environment of this application, hosted on a remote server, and was disappointed to find that the reports were now coming back blank.  After some deeper investigation, it turned out that the data it was retrieving was coming from my development server and not the production server like it had in the past.  As far as I can tell, it is completely ignoring the dataset that I'm assigning to the report object (which is filling with the correct data) and just running the query built into the report, which is connected via ODBC to my development server database.  I have no idea what this is going to do when the application is run from the production environment itself, as in, my customers running the application from their desktops, and I have no way of testing this.<br><br>
I will fully admit that the report may be poorly designed, because then and surely enough now I'm no crystal expert, but as I said in my previous thread, this all worked fine until I upgraded to XI R2 for another project.  Essentially what I want is for the report to accept the dataset and display ONLY that data, and not run a query against the ODBC connection.  Is there some way to force this behavior?  Here's a sample of my code, if it helps:<br><br>
ReportDocument myReport = new ReportDocument();<br>
DataSet myData = new DataSet();<br>
MySqlDataAdapter myAdapter;<br>
myAdapter = new MySqlDataAdapter();<br><br>
file_name = ApplicationMain.file_path"
Files
Invoice_"invoice_number+".pdf";<br>
MySqlCommand cmd = generate_command(invoice_number, false);<br><br>
myAdapter.SelectCommand = cmd;<br>
myAdapter.Fill(myData,"X");<br><br>
myReport.Load(ApplicationMain.file_path+"
Files
Invoice.rpt");<br><br>
myReport.SetParameterValue("requ_id",this.ID);<br>
myReport.SetDataSource(myData);<br>
myReport.ExportToDisk(CrystalDecisions.Shared.ExportFormatType.PortableDocFormat, file_name);<br><br>
It's all relatively simple, create a dataset, load the report, assign the dataset to the report, export to a PDF. 
I've tried to reassign the report's connection to the currently connected database (code snippet below) but every time I end up getting a logon failed error message, even when I know for sure the login data is correct, and even when I'm just connecting to my local development server.<br><br>
TableLogOnInfos crtableLogoninfos = new TableLogOnInfos();<br>
TableLogOnInfo crtableLogoninfo = new TableLogOnInfo();<br>
ConnectionInfo crConnectionInfo = new ConnectionInfo();<br>
crConnectionInfo.ServerName = ApplicationMain.com_host;<br>
crConnectionInfo.DatabaseName = ApplicationMain.com_database;<br>
crConnectionInfo.UserID = ApplicationMain.com_username;<br>
crConnectionInfo.Password = ApplicationMain.com_password;<br><br>
foreach (CrystalDecisions.CrystalReports.Engine.Table CrTable in myReport.Database.Tables)<br>
{<br>
     crtableLogoninfo = CrTable.LogOnInfo;<br>
     crtableLogoninfo.ConnectionInfo = crConnectionInfo;<br>
     CrTable.ApplyLogOnInfo(crtableLogoninfo);<br>
}<br><br>
I ran that after loading the report, but received a failed login error every time.  Any suggestions on how to proceed with this?  I'm at a loss because up until now I've never had a problem like this with a crystal report, they always just took the datasets I gave them without ever running anything else.

Answer 1

After attempting quite a few of the proposed solutions, nothing seemed to be working.  Due to the limited usage and number of reports in my application, I decided to try recreating them from scratch (there are only 3 and 2 are nearly identical) using only the crystal 9 integrated designer in VS2003.  My initial testing has been successful, even using the same base query that the failing reports were using.
Dropping everything and recreating all of ones reports is not the greatest solution, but at worst it's a few hours of tweaking, as opposed to days of frustration messing around trying to get the "corrupted" reports to work again.  Thank you again for your assistance.