If the child has a foreign key to the parent, as it should, you can index the cursor on that foreign key, set a relation, and do your basic 1:M report.

You cannot index a cursor but once, but once is enough.

>The results are 2 cursors, one header and one detail
>
>
>Chris
>
>
>>Christopher,
>>
>>Do you mean that the result of the Select is a flattened file, containing repeating values for the parent and unique values for the children? If so, just group on one of the parent fields.
>>
>>>Anyone know how to get one to many reports to work
>>>where the results are generated form SQL selects into cursors?
>>>
>>>Thanks,
>>>
>>>
>>>Chris