My "way around it" is simple. I NEVER use the view designer - period. It is not difficult to do in code and affords me a lot more control. Since I now have "boilerplate" code for this, I can create a new view very quickly.

Just my .02

Ken

>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 ...