>It is a known bug (VFP 5.0) that when a table has 2 other tables joined to it, the view designer generates an error ...
>
>This is the workaround I use to resolve this bug :
>
>instead of defining the 2nd join as a normal join, I define it in the filter (so it appears in the where clause if the SQL command, instead of in the JOIN clause). I know one of the limitations of using this method is, that this implicits an INNER join (OUTER not possible )
>
>Accept for this limitation, do I have to consider other issues about this method ? (performance, etc ...)
>
>As far as I could find out, stonefield nor eview (sorry eric :-) have an answer to this problem ...

I have been using this method for some time. I found out early on in my view development that the view designer seemed to be programmed by some rookie. Several bugs and several times where it got lost and blamed it on my tables. So when I add any tables I immediately delete the relationship and add my own through the filters.