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

End user reports - Configuration Management How?

edited June 2004 in End User
I've hooked end user reporting into many of our client/server applications.
Now other people in the company are learning to create their own reports. I
don't know how to handle CM now that others have access. Separating into
folders doesn't really help. Any third party tools that plug-in? I use VSS
for source code CM. How is everybody else handling this? Thanks.

Comments

  • edited June 2004

    There are different approaches to this, here are some options:

    1. Use a local database to store the reports. Each user can have their own
    local database to store and retrieve reports.

    2. Implement the TppDesigner.OnCustomOpenDoc and OnCustomSaveDoc events. You
    can additional datafields to the folders and items database tables and store
    and retrieve the security info using these events. (see article below for
    more info on these events).

    3. You might be able to use Queries for the Folders and Items tables to
    select on only the folders and items that you want the user to have access
    to.




    ----------------------------------------------------
    Tech Tip: Using the Designer OnCustomOpenDoc and
    OnCustomSaveDoc events
    ----------------------------------------------------

    The Designer OnCustomOpenDoc and OnCustomSaveDoc events can be used to
    control the loading and saving of reports. For example, you may want to add
    a security feature which does not allow the user to load certain reports.

    When the OnCustomOpenDoc, OnCustomSaveDoc events are assigned, the
    report designer will not save or load any reports - it will instead fire
    the events and your event-handler code will be responsible for taking
    the proper action.

    For example, in ppDsgner.pas there is a method called
    TppDesignerWindow.LoadTemplate that contains the following statement:


    if Assigned(FOnCustomOpenDoc) then
    FOnCustomOpenDoc(Self)
    else
    aReport.Template.Load;


    Note that in the above statement, the Report.Template settings will
    contain the name of the report that is to be loaded etc.

    Likewise the TppDesignerWindow.SaveTemplate method contains the
    following:


    if Assigned(FOnCustomSaveDoc) then
    FOnCustomSaveDoc(Self)
    else
    aReport.Template.Save;




    --

    Nard Moseley
    Digital Metaphors Corporation
    www.digital-metaphors.com



    Best regards,

    Nard Moseley
    Digital Metaphors
    www.digital-metaphors.com
This discussion has been closed.