The one with the filter in the WHERE clause is the "old fashion" and the one with the filter in the FROM clause is the new way. I think the one with the filter in the FROM clause it's the ANSI compatible (or something like that) way of doing joins.

I prefer the ANSI compatible way since its syntax is very much descriptive when you need to use LEFT OUTER JOINS and RIGHT OUTER JOINS.

As far as the result obtained (and performance,) I don't think there is any difference between the two approaches.





>I'm not real familiar with the JOIN clause of VFP's SQL Select command. In the past, I would've done a select like:
>
>sele missacct.acctno, person.lglfname;
> from missacct, family, person;
> into cursor temp;
> where missacct.acctno = family.acctno;
> and family.personno = person.personno;
> and missacct.zip = '49201'
>
>However, I just saw the JOIN clause of the select command and tried this from the command line:
>
>sele missacct.acctno, person.lglfname;
> from missacct;
> join family on missacct.acctno = family.acctno;
> join person on family.personno = person.personno;
> into cursor temp;
> where missacct.zip = '49201'
>
>This yields the same results. I didn't see any notible difference in the speed of the query. But is there any difference in the way those two statements would operate? Is there an advantage of one over the other?