• Doug Lane (10/13/2010)


    Jack isn't saying multiple datasets are bad; he's saying trying to blend multiple datasets in the same table control is bad. RS just wasn't designed to take more than one dataset per control. That said, whether we can all get along or not, gjyothi still would like help.

    If I understand the problem correctly, you want to show something like this:

    Invoice1

    ___MeterInfo1 ... ... ... ...

    ___MeterInfo2 ... ... ... ...

    ___MeterInfo3 ... ... ... ...

    Invoice2

    ___MeterInfo1 ... ... ... ...

    ___...

    If that's the case, I think Jack is right in that it's easier to merge two sets of data on the back end than it is to try to mash them together in RS. If someone has a more efficient hack for that, I'd love to hear it.

    Edit:I just noticed there was a whole second page of posts after I responded, so, um, yeah...sorry about that.

    This is an old post and I suspect the OP is long gone... however... a simple two level hierarchical result set would certainly do the job here. A hierarchyID column (or the equivalent) to sort on would do the job nicely.

    --Jeff Moden


    RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
    First step towards the paradigm shift of writing Set Based code:
    ________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

    Change is inevitable... Change for the better is not.


    Helpful Links:
    How to post code problems
    How to Post Performance Problems
    Create a Tally Function (fnTally)