Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
CODE PROJECT For Those Who Code
  • Home
  • Articles
  • FAQ
Community
  1. Home
  2. Database & SysAdmin
  3. Database
  4. Dynamic Report Generator Framework Design using XML and C# [modified]

Dynamic Report Generator Framework Design using XML and C# [modified]

Scheduled Pinned Locked Moved Database
databasecsharporacledesignregex
3 Posts 2 Posters 1 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • R Offline
    R Offline
    RK KL
    wrote on last edited by
    #1

    Hello experts, I'm trying to design a framework for generating reports by storing the meta data in an XML. The following are the sources (in both SQL / Oracle providers). 1) Tables/Views 2) Stored Procedures 3) OLAP Cubes I'll write a wrapper to sync changes to these Tables/Views/SPs/Cubes so that the XML is up to date. Tables/Views ============ The user will be able to store subset of the columns and filter criteria (1 or many) and should be able to run the same report at a later stage. Stored Procedures ================= Whenever the user wants to run the stored procedure, he/she will supply the parameters and get the output. OLAP Cubes ========== Predetermined cubes and/or cubes with specific members as parameters. I'm thinking the following way using strategy pattern for retrieving data. 1) IReportData: Gets the report data in a dataset/cellset 2) IReportParameters: Gets report parameters (For SPs?) 3) IReportFilters: Report filters / criteria /criteria set 3) IReportSQL: The final executable SQL 4) IReportFormat: Final rendering methodology What do you guys think about this? Do you have any design pattern (s) that you would like to recommend? Thanks, RK.

    You can never try. You either do it or you don't.

    modified on Saturday, September 5, 2009 3:02 PM

    M 1 Reply Last reply
    0
    • R RK KL

      Hello experts, I'm trying to design a framework for generating reports by storing the meta data in an XML. The following are the sources (in both SQL / Oracle providers). 1) Tables/Views 2) Stored Procedures 3) OLAP Cubes I'll write a wrapper to sync changes to these Tables/Views/SPs/Cubes so that the XML is up to date. Tables/Views ============ The user will be able to store subset of the columns and filter criteria (1 or many) and should be able to run the same report at a later stage. Stored Procedures ================= Whenever the user wants to run the stored procedure, he/she will supply the parameters and get the output. OLAP Cubes ========== Predetermined cubes and/or cubes with specific members as parameters. I'm thinking the following way using strategy pattern for retrieving data. 1) IReportData: Gets the report data in a dataset/cellset 2) IReportParameters: Gets report parameters (For SPs?) 3) IReportFilters: Report filters / criteria /criteria set 3) IReportSQL: The final executable SQL 4) IReportFormat: Final rendering methodology What do you guys think about this? Do you have any design pattern (s) that you would like to recommend? Thanks, RK.

      You can never try. You either do it or you don't.

      modified on Saturday, September 5, 2009 3:02 PM

      M Offline
      M Offline
      Mycroft Holmes
      wrote on last edited by
      #2

      You might want to take this to the design forum for a wider response. Ever since I first heard of XML, way back in the 90s, I figured you should be able to use XSLT to format a report and then chuck an xml data file at it for generic type reports. Never followed up on it as I loathe XML.

      Never underestimate the power of human stupidity RAH

      R 1 Reply Last reply
      0
      • M Mycroft Holmes

        You might want to take this to the design forum for a wider response. Ever since I first heard of XML, way back in the 90s, I figured you should be able to use XSLT to format a report and then chuck an xml data file at it for generic type reports. Never followed up on it as I loathe XML.

        Never underestimate the power of human stupidity RAH

        R Offline
        R Offline
        RK KL
        wrote on last edited by
        #3

        Thank you! I posted it in the design and architecture forum. I did not know it was there.

        You can never try. You either do it or you don't.

        1 Reply Last reply
        0
        Reply
        • Reply as topic
        Log in to reply
        • Oldest to Newest
        • Newest to Oldest
        • Most Votes


        • Login

        • Don't have an account? Register

        • Login or register to search.
        • First post
          Last post
        0
        • Categories
        • Recent
        • Tags
        • Popular
        • World
        • Users
        • Groups