In the previous version 2009 Volume 2, my reports where working fine, but since upgrading to Volume 3, each report only shows the first row i.e. only 1 row is shown in the report.
When I design it and preview, I get all rows as expected.
What did you change between these versions which may have caused this behaviour?
Regards, Garry.
Bug Report
Q243967
Visible to All Users
Disclaimer: The information provided on DevExpress.com and affiliated web properties (including the DevExpress Support Center) is provided "as is" without warranty of any kind. Developer Express Inc disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. Please refer to the DevExpress.com Website Terms of Use for more information in this regard.
Confidential Information: Developer Express Inc does not wish to receive, will not act to procure, nor will it solicit, confidential or proprietary materials and information from you through the DevExpress Support Center or its web properties. Any and all materials or information divulged during chats, email communications, online discussions, Support Center tickets, or made available to Developer Express Inc in any manner will be deemed NOT to be confidential by Developer Express Inc. Please refer to the DevExpress.com Website Terms of Use for more information in this regard.
In order to help you track this bug down, I attach a small sample project showing the issue.
There is both an in-project report and an external one.
In both cases setting the .datasource property to a DataSource at run-time to a dynamic dataset results in only 1 row being displayed in the report.
Hi Garry,
Please make sure that you've specified the proper DataSource and DateMember properties.
If it doesn't help you, please provide us with a sample illustrating your issue.
We will examine it, and do our best to help you.
Thanks,
Andrew
Hi Andrew - Thanks for your response, but I did supply a sample project (see below Updated by Garry Lowther at 1/13/2010 4:40:50 PM) before you replied.
Could you please modify the sample to make it work properly as it correctly exhibits the bug you request.
Regards, Garry.
Andrew - I did follow your recommendations and wrote the following code AFTER the .DataSource assignment:
myReport.DataMember = myReport.DataMember
This now works - is this by design?
Regards, Garry.
Hi Garry,
Thank you for the feedback. I see the issue in the attached project.
I'll convert it to the bug report. Our developers will examine it, and do our best to find its cause.
Thanks,
Andrew
Hi Garry,
Thank you for the report. After further consideration we've found that this behavior is caused by the fact that you don't update the DataMember property of your report after updating its data source. Note that for correct operation, your should either provide the same name for your data table or set the DataMember property of your report to the new value, according to your requirements. Please refer to the updated sample in the attachment, and feel free to ask for clarification if necessary.
Thank you,
Valery