Maybe guru RB is neded...

rbuser

I have an application that uses an TppReport+ one DataPipeline;

So at runtime I always can access the data that is provided by the
DataPipeline; I have an report where I have to use as "master dataset" the
recordset provided by this DataPipeline and I need to create a subreport
(showing some detail info) which should retrieve the data from another
source of data;

Remember, the application is already compiled, I cannot access the source
code in order to drop another DataPipeline on the form and to link it to my
"detail dataset"; the only option I have is to use the power of your
integrated DADE so there I can build a query (which can be my "detail
dataset"); Now, is there any way I can "draw" the master-detail relation
between designtime DataPipeline with runtime Query? Well, I know: at runtime
I can create both, master and detail datapipelines as 2 distinct queries and
just establish the master-detail relation; I know this feature, but in the
situation described above I MUST use the designtime datapipeline + "anything
dataset" created with DADE at runtime;



Thanks for your kindly answer.

digitalmetaphors

You can easily link a standard data pipeline to a dataview in DADE, however
linking a dataview to a standard pipeline isn't quite as straightforward
because we need to trick DADE to not try to analyze the link, otherwise it
won't work. Here are the two examples. You'll want the second one:)

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

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


Cheers,

Jim Bennett
Digital Metaphors

rbuser

Jim Bennett, thank you very much for your kindly reply.
Meanwhile I've already used some tricks, I've create a single recorset used
by my design-time DataPipeline which was created base on a SQL UNION, but
each select in UNION has the 1st column as identifier, such as "R1", "R2",
etc;
so I've used the main TppReport and I add some other SubReports that use the
same DataPipeline, and just before DetailBand is generated I've check the
value for this field, and for each report I've shrinked or not the eight of
the DetailBand to 0.001 whenever the record contains or not the identifier
I've expected;
so in some subreports there became visible some detail bands, in some
subreports not;

I've posted this trick in order to tell people that combining RB features +
some smart coding you can get the most amazing report people ever think
about.

Thank you!

digitalmetaphors

Thanks for posting!

--
Cheers,

Jim Bennett
Digital Metaphors