Bret, I haven't done exactly this, but I DID find I had a great deal more flexibility if I painted my table myself instead of using the WWWC functions. I can change colors to highlight certain lines, change formatting in a single cell, etc.

Once you get your cursors, you can do the same thing - painting one table line from your parent cursor, the next 5 from the child cursor etc. Since the code is turned into HTML table code anyway you won't lose any speed. Or if it's all in a single cursor you can watch for changes in your grouping fields.

The easiest way to get the correct code is to do a ShowCursor() call and then look at the raw source with View Source. Copy the header and row items as templates.

Barbara

>I want to put as much as I can into my WWWC-based demo so the client will be persuaded to buy WWWC. I figured out manual paging using .SetSession(). Now I need to combine that concept with grouping. I need to find the most efficient way to cruise my tables and print first a group header (probably with .SendLn()) and then all its children (in some sort of HTML table). I can identify pages in a cursor by comparing RECNO() of a cursor with _TALLY/SomeNumberOfRecordsPerPage. That cursor would have already joined the parent and child tables. But, when making successive group headers and child HTML tables, it would be easier to work with the parent and child tables separately.
>
>If you've worked on this problem already, perhaps you can give me a head start. Thank you.