what are the best practices for using SQL Reporting Services with DevForce?
There are several ways to make use of the Reporting Services and DevForce at the same time.
a) Report goes straight to the database, which means that reports and application actually work with a different data model with all the related problems in implementing and maintaining the solution
b) Report takes the data from a web service. Which might be similar to a) only that we can actually expose the object model through the web service. But maintainance is still quite a hassle.
c) Implementing a data processing extension which provides full support in using reporting services with the data model (but involves quite an investment, but might be the most powerful in the long run)
d) Only doing client side reporting and supplying data from the client. Using simpler rdlc's to directly access the data model but actually loosing quite a lot of the the server features.
I know some of you are also using DevExpress reporting, but we'd prefer Reporting Services if possible.
I am looking forward to exchange some ideas and thoughts on this.