Hello all.

I have a couple general questions.

First, regarding SQL and nested joins.

In MY rather-limited experience with joins, it seems as though Nested Joins often pose major problems, whether it causes VERY slow querying time, or causes the query not to work at all!!!

I had to learn the hard way not only EXACTLY what they were, but just HOW much of a pain they seemed to be.

My question, though, is, with all the evidence to the contrary, is there ever a situation where using nested joins would be PREFERRED???

That having been asked, my next question is about VFP 6.0, specifically the View Designer.

It was using the Designer to form views w/ joins that first introduced me to the problems associated with nested joins. Yet the View Designer, apparently by default, automatically nests them no matter what. We also have even tried creating a view programmatically with a NON-nested join, GENDBCing, and opening up the DBC that we created ... only to see the joins re-nested in the Data Environment.

As far as I/we can tell, there is no way to change this in any type of "preferences" dialog, and it is one of many quirks in regards to the View Designer, IMO the buggiest part of VFP 6.0. Are we correct (about there being no way to change it, that is)?

I hope this is one of many improvements being made to the View Designer for The Next Generation (or whatever they're going to end up calling Version 7).

Thanks all!