K
KJ
I noticed the following behavior:
With 2 repeaters nested, such as:
<asp:repeater id=rptrParentRepeater runat="server">
<ItemTemplate>
<asp:Repeater id="rptrChildRepeater" runat="server"
DataSource="<%#
((DataRowView)Container.DataItem).Row.GetChildRows(RELATION_NAME)%>">
<ItemTemplate>
</ItemTemplate>
</asp:Repeater>
</ItemTemplate>
</asp:repeater>
The DataBinding code in the ASPX pages fires in normal order - that is
to say, it processes the rows in the same order as the select statement
has returned.
However, in the ItemDataBound event in the codebehind, the
ItemDataBound event for the child rows is raised before ItemDataBound
of their parent rows.
I find this odd.
Can anyone explain?
Thanks
-KJ
With 2 repeaters nested, such as:
<asp:repeater id=rptrParentRepeater runat="server">
<ItemTemplate>
<asp:Repeater id="rptrChildRepeater" runat="server"
DataSource="<%#
((DataRowView)Container.DataItem).Row.GetChildRows(RELATION_NAME)%>">
<ItemTemplate>
</ItemTemplate>
</asp:Repeater>
</ItemTemplate>
</asp:repeater>
The DataBinding code in the ASPX pages fires in normal order - that is
to say, it processes the rows in the same order as the select statement
has returned.
However, in the ItemDataBound event in the codebehind, the
ItemDataBound event for the child rows is raised before ItemDataBound
of their parent rows.
I find this odd.
Can anyone explain?
Thanks
-KJ