Hi Trey, thanks for responding.

I can get this technique to work when I use one table with one left outer join, but when I left outer to the other child tables, I start running into trouble as there is now repeated child information. All of the data is captured, but I'm not sure how to then report the data with duplicates from the child tables from conducting the other two outer joins. I hope this makes since. As you can tell I am a little confused here.

John.



>How 'bout this -
>this test assumes that cchild1, cchild2 and cchild3 are all C(10) - hence the use of space(10)
>
>

select par.cparent, ;
>   nvl(tr.cchild1,space(10)) as cchild1, ;
>   nvl(ar.cchild2,space(10)) as cchild2, ;
>   nvl(il.cchild3,space(10)) as cchild3 ;
> from parent par ;
>  left join tracking tr ;
>   on par.cparcelcode = tr.cparcelcode ;
>  left join archive ar ;
>   on par.cparcelcode = ar.cparcelcode ;
>  left join inspectorlead il ;
>   on par.cparcelcode = il.cparcelcode ;
> into cursor cureport

>
>>Hi all,
>>
>>Unfortunately I don't get to work with VFP as much as I used to and
>>I've been busting my brain for a couple of hours now trying to figure out how in the world to get this one-to-many report to work.
>>
>>I have a parent table with three (many) children tables(tracking,archive,inspectorlead). These child tables are holding tracking and archived information and are related to the parent by a parcel code field. What I need is a report that shows the parent information and all of the entries from each of these tables. There could be from 0 to possibly 10 detailed records in anyone of these three children tables. I can get this to work with only one of the three tables (querying into one cursor), but add the other two and things go horribly wrong. I would like to use a cursor or a view as my data source so that relations are not needed other than to query the data.
>>
>>I would appreciate any ideas from the experts!
>>
>>Thanks.
>>
>>john.