This is a migrated thread and some comments may be shown as answers.

Best Practices for Consuming Reports in Multiple Clients

0 Answers 35 Views
General Discussions
This is a migrated thread and some comments may be shown as answers.
Paul Patterson
Top achievements
Rank 1
Paul Patterson asked on 12 Nov 2010, 05:01 PM
Hi all!

Rather than try and re-invent the wheel...

I have a solution that includes a number of projects including; winform, web, and mobile clients. I also have a separate class for my reports. I also have abstracted interfaces for business logic, and also others for business objects and data access. Nothing really unusual here.

What I am looking to do is provide my users with a catalogue of reports, which will be displayed to them via a treeview control grouped by headings (parent nodes). I've considered these possible implementations:

  • Using a database in which I built two tables that include a Report table and a ReportGroup table. This can be used to build the treeview control on the form. Doing this would allow me to control what reports are made available to specific customers. 
  • Through reflection, iterate through the report classes within the report assembly, and then build the treeview using the attributes of each found report class.
  • Build a custom config file that does the same as the above.

Does anyone have any example implementations of any of these? If so, please post some examples. 

Much appreciated!

Paul

No answers yet. Maybe you can help?

Tags
General Discussions
Asked by
Paul Patterson
Top achievements
Rank 1
Share this question
or