>Try it like this:
>
>SELECT Employee.*, Fruits.fruit, Vegies.vegetable;
> FROM vegies;
> RIGHT OUTER JOIN fruits;
> RIGHT OUTER JOIN employee ;
> ON Employee.id = Fruits.id
> ON employee.id = vegies.id
>

>>
>Having said all that, I think the sequential syntax is a much better choice here. It makes much more sense to the reader and, in the long run, will be easier to maintain.
>
>Tamar


Tamar,
Thanks for explaining it so well. This works. I also totally agree with you on the sequential syntax. It is much more intuitive. My real problem was not in FoxPro but with an ADO connection to an AS400 table where I had a problem with a similar query (one parent and multiple child tables) that I wrote in sequential style and I tried rewriting it in nested style thinking that ODBC may prefer nested and that gave me even a worse result. It turned out that the style was not the culprit. Thanks.