Home/ Questions/Q 123049
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-11T04:13:31+00:00

I’m trying to populate a DataTable, to build a LocalReport, using the following: MySqlCommand

  • 0

I’m trying to populate a DataTable, to build a LocalReport, using the following:

MySqlCommand cmd = new MySqlCommand(); cmd.Connection = new MySqlConnection(Properties.Settings.Default.dbConnectionString); cmd.CommandType = CommandType.Text; cmd.CommandText = 'SELECT ... LEFT JOIN ... WHERE ...'; /* query snipped */  // prepare data dataTable.Clear(); cn.Open(); // fill datatable dt.Load(cmd.ExecuteReader()); // fill report rds = new ReportDataSource('InvoicesDataSet_InvoiceTable',dt); reportViewerLocal.LocalReport.DataSources.Clear(); reportViewerLocal.LocalReport.DataSources.Add(rds);

At one point I noticed that the report was incomplete and it was missing one record. I’ve changed a few conditions so that the query would return exactly two rows and… surprise: The report shows only one row instead of two. I’ve tried to debug it to find where the problem is and I got stuck at

 dt.Load(cmd.ExecuteReader());

When I’ve noticed that the DataReader contains two records but the DataTable contains only one. By accident, I’ve added an ORDER BY clause to the query and noticed that this time the report showed correctly.

Apparently, the DataReader contains two rows but the DataTable only reads both of them if the SQL query string contains an ORDER BY (otherwise it only reads the last one). Can anyone explain why this is happening and how it can be fixed?

Edit: When I first posted the question, I said it was skipping the first row; later I realized that it actually only read the last row and I’ve edited the text accordingly (at that time all the records were grouped in two rows and it appeared to skip the first when it actually only showed the last). This may be caused by the fact that it didn’t have a unique identifier by which to distinguish between the rows returned by MySQL so adding the ORDER BY statement caused it to create a unique identifier for each row.
This is just a theory and I have nothing to support it, but all my tests seem to lead to the same result.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. I had same issue. I took hint from your blog and put up the ORDER BY clause in the query so that they could form together the unique key for all the records returned by query. It solved the problem. Kinda weird.

    • 0