Is data shaping slower and more intensive than manually getting recordsets and parsing your way through it to write the data the way you want? <BR><BR>Wouldn&#039t so many nested recordsets be inefficient? How well does this perform under load?<BR><BR>I have written several applications where this approach would be fitting, but an concerned about the number of recordsets returned. Currently, we are using a working (WIP) table in SQL server to create a hierarchical ordered set of data before sending the single recordset back to ASP. With the data now <BR>ordered based on parent relationship, I can iterate through it in script, writing out each record in a format relative to the previous record (ie, its parent or sibling).<BR><BR>How would multiple nested recordsets be a better method?<BR><BR>Thank you.<BR>