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

Basing a report on the current record

edited June 2001 in General
Is it possible to have a report based upon the current record of multiple
datasets that are linked in a multiple parent/child relationship which is at
least three levels deep and where all of the nested relationships are
one-to-one?

Comments

  • edited June 2001
    Please let me rephrase that:

    Is it possible to have a report based upon the current record of multiple
    datasets that are linked in a parent/child relationship which is at
    least three levels deep and where all of the nested relationships are
    one-to-one?





  • edited June 2001
    There is the concept of master-detail-detail, such as you would get from
    linking the Customer-Orders-Items data tables. See the main demo project in
    your installation../RBuilder/Demos/1. Reports and look at demos #71-73 You
    can also create master-detail-detail linking relationships in DADE.


    Cheers,

    Jim Bennett
    Digital Metaphors


  • edited June 2001
    Hi Jim.

    Please forgive the "on the fly" questions. I am thinking about current
    project requirements and wanted to get a quick answer.

    I do understand the concept of master-detail-detail. What I am unsure of is
    whether that master-detail-detail can be maintained for the current record
    across the master-detail-detail relationship.

    Consider an example where I am using the bound tree control from Infopower.
    The Master-detail-detail would be maintained for the current record out to
    the deepest level. That is, while the tree shows the master-detail-detail
    and the existing one-to-many records, it allows the selection of a detail
    record only - such a the deepest node (i.e., detail1) where the relationship
    is master-detail1- detail2.

    Now, given that the Master-detail-detail may have one-to-many existing
    records across the links, I want to construct a report that would limit the
    data output to the current record (as the bound tree does) of each of the
    datasets in the Master-detail-detail linked relationship. Further, the
    report and the bound tree would be tied to the same datasets - so, I would
    be creating a report using the same datasets as the controls within the
    application interface.

    I seem to recall that there is a property setting that determines whether
    one or multiple records are printed - maybe that is what I am looking for
    here. Such a setting would prevent printing all the records on the "many"
    side of the one-to-many relationship.

    Jim, I hope that is a better explanation of what I want to do. I know . . .
    it's not a complicated question, but I thought I could impose on your
    support to give me a quicker answer than I could get be running a test.

    Regards,

    Wayne

  • edited June 2001
    Hi,

  • edited June 2001
    Thanks, Ronald.

    Regards,

    Wayne


  • edited June 2001
    I do that here and set the [Begin Range] and [End Range] of the
    ppDBPipleine components as required. For the parent that would
    as rbCurrentRecord and reCurrentRecord. To avoid refreshes
    to the grids on my forms when the report uses the same data
    connections I do a few .disablecontrols / .enableconstrols on
    the table components.

    Brian Evans

  • edited June 2001

This discussion has been closed.