You are SO right!! I've saved MORE time by working the correct cursor out in a test PRG and then just sending it to the report than I can count.


>Just wanted to mention that this is the technique I prefer.
>
>IMHO, doing some work in the code to build the cursor properly and then sending the report straight forward information (as far as the report is concerned) is always easier than sending reports the unprocessed information and trying to do the processing in the report.
>
>Take care,
>Joe
>
>>Galia,
>>Use a cursor instead of the parent/child tables, so that all the data is in the same cursor. You can add a field and fill it with '1' for the first child, '2' for the second, etc. Then use ORDER BY with this field to order the results.
>>
>>HTH
>>Barbara
>>
>>>Is there any way the data from several child tables to show in the band "Detail" in the Report Designer ?
>>>
>>>I have one parent table which is related to four other child tables. I want to show all matching records from first child table in the band "Detail", under those records I want two place all all matching records from second child table in the band "Detail" etc.
>>>
>>>
>>>
>>>Sincerely,
>>>
>>>Galia Cvetkova