By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
459,296 Members | 1,446 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 459,296 IT Pros & Developers. It's quick & easy.

Nested Repeaters: ItemDataBound fires in reverse order (hierarchical data)

P: n/a
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

Nov 19 '05 #1
Share this question for a faster answer!
Share on Google+

This discussion thread is closed

Replies have been disabled for this discussion.