Home General
New Blog Posts: Merging Reports - Part 1 and Part 2

Reports Saved in a Database

edited January 2002 in General
i'm still fuzzy on 1 point, even after reading your documentation:

If using the Enterprise version, can a report's layout, code and
calculations can be saved in a database table row. Just save the whole
layout in a Memo or BLOB field?

Say i have 50 users of a Delphi EXE, running 3-tier via the internet and
Datasnap, to a MSSQL database. Does this mean i can change the
positioning of a label, or any part of a report, save that change to the
db column in Sql Server, and the user can then download the change,
through datasnap, and run the updated report?

Would they have to download the report each time they use it, or could
its' layout be saved in a client-side data set? are there any
limitations for running this through DataSnap (or even ASTA)?

If possible, this is just huge - especially because our reports change
so often and there will be lots of users around the country... Thanks

Alex

Comments

  • edited January 2002
    Our end user solution demos have scripts which create the report table
    called Items. The report explorer uses an Item datapipeline to get the
    reports from the Items table. You can use the Report.Template's methods
    which can load and save itself to a database table. You can update the db
    with a new template, and your users can print the latest report that exists.
    If the data acces, code, and layout are saved in the template, then you do
    not have to recompile your exe.

    Cheers,

    Jim Bennett
    Digital Metaphors


  • edited February 2002
    Can you point me to the end user report that demonstrate this capability?

This discussion has been closed.