Master Detail with the daMidas DADE plug-in

rbuser

I'm using the daMidas DADE plug in with Report Builder Enterprise version
7.0. It works great if I create a single data view, but if I link two data
views together in an attempt to do a master/detail report, I get the master
information but only the first line of each detail item. I'm kind o' new to
the three tier world, but I'm guessing that this limitation has something to
do with the fact that all of the data is being drawn through the 'Dummy'
query set up in the data server, and it appears the daMidas code doesn't do
anything to set up master-detail relationships on the client data sets.

Am I on the right track? If so, how would I go about creating the
master/detail info on the client side based on the data views the end user
has created?

I would appreciate any advice or direction.

Thanks,

Richard P. Kelly.

digitalmetaphors

You would need to build queries that we normally would have constructed. We
build SQL in the details that only fire once, in order to return all detail
records for all masters in one dataset in hte proper order (by the master of
course). So, if you can construct the detail dataview to be a dataset the
joins the master table and the detail table and then orders by all the
master's order bys then your detail tables' order by's itshould be
supportable by manually linking the dataviews in code. The dataview
architecture creates data access components behind the scenes, but
inreality, all we need to get is the data pipeline that the dataview
creates. Once the pipeline is extracted from each dataview, you can "link"
them in code by using the MasterDatapipeline and MasterFieldLinks
properties. Here is an example using the BDE:

http://www.digital-metaphors.com/tips/LinkEditSQLDataviews.zip


Cheers,

Jim Bennett
Digital Metaphors