>>You may be making the same mistake that I keep seeing people make with multiple detail bands. If all you have is one parent record ... and then another table with child records ... you do NOT have a situation for multiple detail bands. What you should be doing is driving the report with the child table and have a relation to the parent table. Create a data group on the field that matches up with the parent. Put all the parent information in the data group header band. Put all the child information in the detail band. No need for a second detail band.
>>
>>Two detail bands are meant to be used in the situation where you have 3 tables .. a parent table, a child table, and a completely different child table. For example, a Customer table would be the parent and its information is placed in a Data Group Header band. An Order table would be the first child table showing all the orders from a customer and its information is stored in the Detail 1 Band. A Payment table would be the second child table show all the payments from a customer and its data is stored in the Detail 2 Band. There isn't necessarily a relationship between ORDERS and PAYMENTS.
>
>Hi Cathy,
>
>If I have a parent, child and a grandchild, how can I make this report to work? I used to always print from one combined cursor instead...

2-detail band could be useful only if you have more than one member on some relational level. For example, parent-child-2 grandchilds. Before it was solved by either using 'generic' cursor fields, or by 'overlapped' report fields.
If every relational level has only one member then it's just an issue of adding more grouping levels.