What is a typical scenario for and end-user reports design?

Posted by Sebastian on Stack Overflow See other posts from Stack Overflow or by Sebastian
Published on 2009-07-29T02:00:37Z Indexed on 2010/04/17 7:23 UTC
Read the original article Hit count: 345

Filed under:
|
|
|

Hello!

I'm wondering what would be the typical scenario for using an end-user report designer. What I'm thinking of is to have a base report with all the columns that I can have, also with a basic view of the report (formatting, order of columns, etc.) and then let the user to change that format and order, take out or add (from the available columns) data to it, etc.

Is that a common way to address what is called end-user designer for reports or I'm off track?

I know it depends on the user (if it's someone that can handle SQL or not for example), but is it common to have a scenario where the user can build everthing from the sql query to the formatting?

Thanks!

Sebastian

© Stack Overflow or respective owner

Related posts about reports

Related posts about ASP.NET