Mike,

I have found a workaround for this problem which will allow you to build your view entirely in the view designer (with more than one joined table).

Don't let VFP define the joins for you when you add your tables and don't make your joins in the join tab - use the filter tab instead and just join your tables using the "where" clause (just like the pre-5.0 days). Then you won't get that error.

The following filter tab example joins a parent and two child tables and filters the result with 2 filter parameters:

filter expression:
parent.keyfield is equal to child1.foreignkeyfield .AND.
parent.keyfield is equal to child2.foreignkeyfield .AND.
parent.filterfield1 is equal to ?ViewParameter .AND.
parent.filterfield2 is equal to ?ViewParameter2

If you insist on using the join syntax, you'll have to create your view programmatically but this workaround seems to do the job quite well within the view designer.

-JT