PJ Rodriguez
Top achievements
Rank 1
Rank 1
PJ Rodriguez
asked on 12 Mar 2011, 01:04 AM
I moved my Telerik Reporting Project to a different workstation. I edited the datasources of the database that I was connecting to to reflect the new location. I tested each datasource to make that it connects and is able to preview data.
However, my parametized reports no longer work.
I troubleshot this further and found that it's actually the upgrade from Telerik Reporting 2009 Q3 to 2010 Q3 that causes the failure. There are no errors during the upgrade. When I compile, however, there are warnings about obsolete codes. Would that be the cause?
PJ
However, my parametized reports no longer work.
I troubleshot this further and found that it's actually the upgrade from Telerik Reporting 2009 Q3 to 2010 Q3 that causes the failure. There are no errors during the upgrade. When I compile, however, there are warnings about obsolete codes. Would that be the cause?
PJ
1 Answer, 1 is accepted
0
Hello PJ Rodriguez,
Prior Q1 2010 Telerik Reporting did not provide its own data layer but depended on the existing .NET objects (DataSet, Data Table, DataView, ADO.NET, lists. Because of that, the Telerik Reporting Data Source Wizard could not be used to connect to parameterized data source such as stored procedure or a Select command with parameters out of the box.
However in Q1 2010 we have introduced Data Source Components and this is the suggested way to proceed from now on. You can still use DataSet, Data Table, DataView etc. as a data source but you should create it by yourself. If you choose to proceed this way, the ObjectDataSource is the way to go.
Anyway if your reports display data from a database, instead of using DataSets and DataTables we suggest using the SqlDataSource component that is designed to work especially with Telerik's reporting engine thus offering much better performance.
Generally when making such drastic upgrade (one year time), we highly recommend reviewing the release history for listed breaking changes, new features and fixes that change/improve the behavior of the product.
Kind regards,
Steve
the Telerik team
Prior Q1 2010 Telerik Reporting did not provide its own data layer but depended on the existing .NET objects (DataSet, Data Table, DataView, ADO.NET, lists. Because of that, the Telerik Reporting Data Source Wizard could not be used to connect to parameterized data source such as stored procedure or a Select command with parameters out of the box.
However in Q1 2010 we have introduced Data Source Components and this is the suggested way to proceed from now on. You can still use DataSet, Data Table, DataView etc. as a data source but you should create it by yourself. If you choose to proceed this way, the ObjectDataSource is the way to go.
Anyway if your reports display data from a database, instead of using DataSets and DataTables we suggest using the SqlDataSource component that is designed to work especially with Telerik's reporting engine thus offering much better performance.
Generally when making such drastic upgrade (one year time), we highly recommend reviewing the release history for listed breaking changes, new features and fixes that change/improve the behavior of the product.
Kind regards,
Steve
the Telerik team