> I'm working on a generic solution for application reports and have
> decided that our best option is to use ADO.NET for the report source
> and have also decided that we will distribute the reports at runtime
> via a web service.

> 1. Does anyone have any experience with modifying a report that is
> deployed via a web service?  It seems very easy (too easy) to deploy
> if the database you designed your reports on is your production
> database (but developing in production is a bad idea).  How do you
> change the database connection at runtime (when it is a web service
> report)?

> 2. Again, if you are deploying via a web service, where do you put the
> code to populate the ADO.NET dataset and set the report's datasource?
> This may be the same question as #1.

> 3. I have seen how easy it is to deploy an existing report with no
> login info via a web service.  How would I go about designing a web
> service that could deploy any report?  The confusing issue is how the
> consumer accesses the web service by merely setting the ReportSource.
> Too much smoke and mirrors for me :).

> TIA,
> Jim