>No, you're right. SQL won't work. This is because the SELECT returns
>the cartesian product of the results. But then, this is exactly what
>you described. Foxfire! will haev the same result because it is a
>wrapper around the FoxPro functionality, and it uses SQL to retrieve the
>results as well.
>
>Are you looking to do all names, or just one of them? Do the addresses
>always have single line, or are there some cases where you have to deal
>with multiple lines?
>
>I can't think of any way that SELECT can handle this gracefully. I
>think you'll have to resort to procedural code.
>
>/Paul
>
>> I have 3 tables
>>
>> name having names of persons
>> address having addresses of persons
>> contact having contact nos. of persons
>>
>> name is parent which is related with address by code & it is also related
>> with contact by code.
>>
>> Its one parent and 2 childs.
>>
>> I want simply a report like this :-
>>
>> name contact1 address1
>> name contact2 address2
>>
>> I have one record in name, 2 in contact and 2 in address, the right result
>> should come as 2 records

Actually your answer has given me a satisfaction, that what I'm not able to do through SQL, same applies to a commercial product.

The same type of structure, I have in my one more project:-

Order is the main/parent order files
delivery is the delivery dates realted with order
Lc file is having all the lc details of a particular order
nego file contains all the details of negotiations of that order..

Still the list is long.. but you see the problem is same..

one parent and so many childs.. :)

I guess procedural code is the only solution for that....

Thanks again for your reply