Hello,
I am aware of the datasource problems posted latley but wanted to make sure you were aware of a few concerns of mine.
When trying to add a datasource to the report via the report's DataSource property, I chose Database datasource type in the wizard. I then connect to a SQL 2000 database and then am given the option to use tables or views in my report. What about SQL Server stored procedures? Will those be supported?
Also - if you set your report's DataSource to a dataset and then delete that dataset in the designer view, the report's DataSource property doesn't automatically update to reflect that. If you try to change the DataSource property in the properties box, you get 'Object not an Instance' error.
Justin
I am aware of the datasource problems posted latley but wanted to make sure you were aware of a few concerns of mine.
When trying to add a datasource to the report via the report's DataSource property, I chose Database datasource type in the wizard. I then connect to a SQL 2000 database and then am given the option to use tables or views in my report. What about SQL Server stored procedures? Will those be supported?
Also - if you set your report's DataSource to a dataset and then delete that dataset in the designer view, the report's DataSource property doesn't automatically update to reflect that. If you try to change the DataSource property in the properties box, you get 'Object not an Instance' error.
Justin
4 Answers, 1 is accepted
0
Hello justins,
It seems that we've missed to handle correctly the case when deleting the instance that is assigned to the Report.DataSource. We logged this issue in our bug tracking system and will fix it for the next version/service pack.
For particular reasons we left the support for stored procedures in the Connect Data Source Wizard for the next versions. Some of our concerns are how to handle a stored procedure that returns multiple result set; how to set the parameters of a stored procedure, etc.
Greetings,
Svetoslav
the telerik team
Instantly find answers to your questions at the new Telerik Support Center
It seems that we've missed to handle correctly the case when deleting the instance that is assigned to the Report.DataSource. We logged this issue in our bug tracking system and will fix it for the next version/service pack.
For particular reasons we left the support for stored procedures in the Connect Data Source Wizard for the next versions. Some of our concerns are how to handle a stored procedure that returns multiple result set; how to set the parameters of a stored procedure, etc.
Greetings,
Svetoslav
the telerik team
Instantly find answers to your questions at the new Telerik Support Center
0
Russell
Top achievements
Rank 1
Rank 1
answered on 01 Oct 2007, 05:18 PM
Any time frame for when Reporting will be able to handle stored procedures?
0
Justin White
Top achievements
Rank 1
Rank 1
answered on 02 Oct 2007, 03:07 PM
Hi Eric,
For what it is worth - we were able to use stored procedures by simply putting "exec [sproc name here]" in the SQL statement text box while creating the report.
Hardly an optimal solution for all sorts of reasons (and I haven't tried it with parameters although I highly doubt it works) but it solved a big problem for us in that our security model does not allow anyone direct access to the tables.
Cheers,
Justin White
City of Eugene
For what it is worth - we were able to use stored procedures by simply putting "exec [sproc name here]" in the SQL statement text box while creating the report.
Hardly an optimal solution for all sorts of reasons (and I haven't tried it with parameters although I highly doubt it works) but it solved a big problem for us in that our security model does not allow anyone direct access to the tables.
Cheers,
Justin White
City of Eugene
0
Hi Eric,
Currently it is possible to use stored procedures but you have to create the data adapter by hand and then use it as report data source. Please review this help topic for more information.
Using stored procedures is a little bit more complicated than a sql query because they usually accept parameters. We're currently developing report parameters (already started with Q2 2007) and will continue to polish them for the next release - Q3 2007. Once we finish the mechanism to pass parameters to the report (and data source probably) we'll continue with the stored procedure support by the data source/report wizards.
Best wishes,
Svetoslav
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center
Currently it is possible to use stored procedures but you have to create the data adapter by hand and then use it as report data source. Please review this help topic for more information.
Using stored procedures is a little bit more complicated than a sql query because they usually accept parameters. We're currently developing report parameters (already started with Q2 2007) and will continue to polish them for the next release - Q3 2007. Once we finish the mechanism to pass parameters to the report (and data source probably) we'll continue with the stored procedure support by the data source/report wizards.
Best wishes,
Svetoslav
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center