Thanks Cetin for the late night response.

I have two problems with this:
1: the SELECT - SQL which I will think about later when I am more awake, and;
2: the childrens data can not be listed on the same row it must be:
Parent rec1 info (and only record)

TITLES
child1 rec1 info
child1 rec2 info
child1 rec3 info

TITLES
child2 rec1 info
child2 rec2 info

Thoughts???

>Ian,
>If one parent and two child, then you would have 4 recs for that parent record, the last two with NULL values for the second child. And these would fit under correct headings.

Parent rec group header
>Header for child1                               Header for child2
>child1 rec1                                     child2 rec1
>child1 rec2                                     child2 rec2
>child1 rec3
>child1 rec4

Cetin
>
>
>
>>I thought I understood and maybee I'm just tired (likely) but after creating a joined table I could not resolve the prob.
>>
>>I wrote my original request in great haste. Here is a 'better' version of the question. I have 1 parent and 2 child tables that must go to a report.
>>
>>VFP can not create two DETAIL sections for DATA GROUPING so the suggestion is(?) to create a CURSOR with SELECT SQL to merge the two children into one for report purposes.
>>
>>My problem then is that I don't understand how to separate out the info from the CURSOR for the report. For instance if I have 4 matching records in child#1 and 2 matching records in child#2 my CURSOR will have 6 records. How can I tell VFP to print the first 4 of those records under one set of headings and to print the remaining 2 under another set of headings?
>>
>>i.e.
>>
>>John Doe ............ From Parent Table
>>250 6th St
>>Alberta, Canada
>>
>>-------------
>>DETAILS
>>AA BB CC ........... From the Cursor Table
>>18 17 60
>>20 25 1000
>>60 80 620
>>70 90 600
>>
>>-------------
>>PARTNERS
>>NAME ADDRESS ........ From the Cursor Table
>>BigB 100 Somewhere Pl
>>LilJ 200 There Lane
>>
>>
>>Maybe I am looking for a quick fix and there is not one. Am I oversimplifying this issue???
>>
>>
>>
>>>Right, and sometimes when I need to change something in the cursor before printing I just REPLACE FOR ISNULL(somefield) WITH 0 (first of all, of course the cursor needs to be made uptatable).
>>>
>>>Nick
>>>
>>>>And, of course, you'll need to check the values with isnull() to handle them.
>>>>
>>>>>I have the Statement report which works the way similar to what Barbara says.
>>>>>It is based on the SQL cursor made of 4 JOINed tables. It is grouped by company key, and invoice key. The invoice information is in the group header, the multiple payments info (for this invoice) goes into the Detail band.
>>>>>BTW, after the join many fields in the cursor may have NULL values.
>>>>>
>>>>>HTH,
>>>>>
>>>>>Nick