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. Database & SysAdmin
  3. Database
  4. Pluggable Reports

Pluggable Reports

Scheduled Pinned Locked Moved Database
cssarchitecturequestion
1 Posts 1 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.
  • P Offline
    P Offline
    ProffK
    wrote on last edited by
    #1

    I'm wondering what the best way to implement plug-in reports is. If I use Crystal, which I haven't for over a year, I have the benefit of built-in selection parameters, so I could possibly get away with just 'dropping' the report files into a store, and having my code pull the full report name from the file somehow. The report itself will then handle the selection parameters. If I do a custom solution, I could follow a plug-in assembly architecture, where each report is packaged as its own class library, with a custom selection screen1 and output grid. 1. Anyone recognise this ABAP/4 term? I used to get high on life until I realized that life was cut with morons - Unknown

    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