Crystal Reports Field Mismatch

[Former Member]

Hello All,

Certain reports in my application are changing field positions at runtime. In design view the fields are positioned correctly but at runtime they somehow change. The labels remain in the correct position but the fields displaying data move. This happens in the details as well as header sections. I have tried to re generate the data set and verify the database to no avail. The only way i can fix this is by using formula fields to refer to the data set fields i wish to display.

What I mean is that if I have two fields, adate and atext, the data from adate displays in the atext field and vice versa. There is no custom code that i can see in the report that would swap the two fields...

I am working with Visual Studio 2005

Crystal Reports 2005 Service Pack 1

Data sets are getting populated from SQL Server 2005

I am using the Set Data Source method to set the tables for the report.

I have also tried to update the solution and reports to Visual Studio 2008, but that also did not work.

Edited by: Bruceo123 on May 7, 2010 8:29 AM

[former_member11696 · Accepted solution]

Hi Bruce, the reason the fields are moving is because the report fields do not match the fields of the data set. CR will auto-delete any fields it can't map. Only option at this point is to verify your reports and then work with known verified reports.

[Former Member]

Hi;

Make sure the dataset structure is not changing at all. Try running a Verify Database from the report.

See the following:

/people/ludek.uher/blog/2009/03/02/troubleshooting-issues-with-vs-net-datasets-and-crystal-reports

Regards,

Jonathan

Follow us on Twitter u2013 http://twitter.com/SAPCRNetSup

[Former Member]

Hi Jonathan,

Thanks for your feedback.

I have tried to re generate the dataset (as described in the link), set the datasource location and then update. This does not fix the issues. The only way i am able to fix the report is to go to the database expert, remove all the tables and then re add them again.

Obviously this is not ideal because I lose all my database fields and their formatting on the report.

Regards

Bruce