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
  1. Home
  2. Other Discussions
  3. IT & Infrastructure
  4. Recommded Reporting components

Recommded Reporting components

Scheduled Pinned Locked Moved IT & Infrastructure
databasetools
2 Posts 2 Posters 0 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.
  • D Offline
    D Offline
    dwolver
    wrote on last edited by
    #1

    Looking for component suites for reporting tools that other developers recommend 1 not database dependent, ie can use objects 2 Allows for dynamic creation of reports, subreports etc 3 Supports both windows and web using common report engine

    U 1 Reply Last reply
    0
    • D dwolver

      Looking for component suites for reporting tools that other developers recommend 1 not database dependent, ie can use objects 2 Allows for dynamic creation of reports, subreports etc 3 Supports both windows and web using common report engine

      U Offline
      U Offline
      User 3677987
      wrote on last edited by
      #2

      For mostly alphanumeric reports, I suggest you use the regular IO functions of your language to generate HTML. This can be viewed and printed in the browser. I wrote a Windows app that generated invoices that way, and that part of the system turned out really well. Obviously, this is a workable approach for a web-based app. If you're trying to do something with dynamic graphics (charts, graphs, etc.) the HTML approach won't work so well. But I still advise you to - as much as possible - just stick with the built-in capabilities of your main language. As for dedicated reporting tools, I've used several and I can't recommend any of them. The two with which I have the most experience are Brio (a.k.a. SQR) and Crystal Reports. Brio was tolerable but I never really saw the point. When using it, I never got the sense that it was making me more productive compared to, say, STDIO.H or IOSTREAM.H. Crystal Reports is just bad... it's difficult to install and deploy, overly abstract and graphical, bloated, and unreliable. The HTML-based approach I suggested above actually grew out of a failed attempt to stand up a Crystal environment for the project. If you absolutely must use a dedicated reporting tool, I definitely suggest you avoid any of the slick-looking "Business Intelligence" tools that seem to be in vogue. Examples are Cognos and Business Objects. I think these Business Intelligence companies survive by taking a slick sales appeal straight to management ("here's how you can dynamically create slick looking reports from your desk without any tech skills..."). Managers seem to think reports should be easier to make and should look better... frankly, they're wrong. Reports are application programs and will always suffer from the difficulties associated with application programming.

      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