S
senfo
I've been trying to come up with a way to use the built in ASP.NET
controls to design something that displays the results of a database
query by group like is possible in an Access report to, for example,
display a list of managers and all of their employees. For example:
Type 1
Column 1, Column 2, Column 3
Column 1, Column 2, Column 3
Column 1, Column 2, Column 3
Type 2
Column 1, Column 2, Column 3
Column 1, Column 2, Column 3
Column 1, Column 2, Column 3
Type 3
Column 1, Column 2, Column 3
Column 1, Column 2, Column 3
Column 1, Column 2, Column 3
[...]
So far, I have come up short on ideas to implement this cleanly using
the ASP.NET controls. A friend of mine suggested a Repeater with
another Repeater nested inside of it; however, it just didn't seem like
a clean way.
I've considered developing my own custom server control that extends the
CompositeDataBoundControl class, but even doing this, I couldn't think
of a clean way of doing it without requiring two DataSource properties
(one for the Managers and another for the Employees).
I'm sure others have run across a similar situation in the past; but, I
haven't had any luck locating any examples.
Does anybody have any suggestions?
Thank you in advance,
controls to design something that displays the results of a database
query by group like is possible in an Access report to, for example,
display a list of managers and all of their employees. For example:
Type 1
Column 1, Column 2, Column 3
Column 1, Column 2, Column 3
Column 1, Column 2, Column 3
Type 2
Column 1, Column 2, Column 3
Column 1, Column 2, Column 3
Column 1, Column 2, Column 3
Type 3
Column 1, Column 2, Column 3
Column 1, Column 2, Column 3
Column 1, Column 2, Column 3
[...]
So far, I have come up short on ideas to implement this cleanly using
the ASP.NET controls. A friend of mine suggested a Repeater with
another Repeater nested inside of it; however, it just didn't seem like
a clean way.
I've considered developing my own custom server control that extends the
CompositeDataBoundControl class, but even doing this, I couldn't think
of a clean way of doing it without requiring two DataSource properties
(one for the Managers and another for the Employees).
I'm sure others have run across a similar situation in the past; but, I
haven't had any luck locating any examples.
Does anybody have any suggestions?
Thank you in advance,