How would seasoned ReportBuilder report developers approach the following reporting requirement cons
Hi,
How would seasoned ReportBuilder report developers approach the following
reporting requirement considering the source data?
In simple terms I have some tables that looks something like this:
TableA: ID1
TableB: ID1 ValueA1 ValueA2 ValueA3
TableC: ID1 ValueB1 ValueB2 ValueB3
TableD: ID1 ValueC1 ValueC2 ValueC3
TableA is the master with ID1 being the unique key. All the other tables
have zero or more rows for each ID1 in TableA (and no unique key).
In simplistic terms, the end-user wants the following report layout:
Group[TableA.ID1]
SubReport1[TableB]
SubReport2[TableC]
SubReport3[TableD]
That is, for each ID1 in TableA, generate three sub reports. Each of these
sub reports are to display the data for the current ID1 only.
Any tips and tricks would be very much appreciated.
-Andreas
How would seasoned ReportBuilder report developers approach the following
reporting requirement considering the source data?
In simple terms I have some tables that looks something like this:
TableA: ID1
TableB: ID1 ValueA1 ValueA2 ValueA3
TableC: ID1 ValueB1 ValueB2 ValueB3
TableD: ID1 ValueC1 ValueC2 ValueC3
TableA is the master with ID1 being the unique key. All the other tables
have zero or more rows for each ID1 in TableA (and no unique key).
In simplistic terms, the end-user wants the following report layout:
Group[TableA.ID1]
SubReport1[TableB]
SubReport2[TableC]
SubReport3[TableD]
That is, for each ID1 in TableA, generate three sub reports. Each of these
sub reports are to display the data for the current ID1 only.
Any tips and tricks would be very much appreciated.
-Andreas
This discussion has been closed.
Comments
like you say yourself,
1 group (table A)
3 subreports tied to the Table A sql (so when the master changes, the detail
queries change also)
cu
marc
wasn't.
-Andreas