>Because you use an INNER JOIN,
>this:
>

>SELECT Member.Numero,Status.Numero FROM Member;
> INNER JOIN Status ON Member.NoStatus=Status.Numero;
> WHERE Member.NumeroI=4112;
> ORDER BY 1 ASC
>

>
>is equal to:
>

>SELECT Member.Numero,Member.NoStatus FROM Member;
> INNER JOIN Status ON Member.NoStatus=Status.Numero;
> WHERE Member.NumeroI=4112;
> ORDER BY 1 ASC
>

>
>If Status.Numero is indexed,
>the exists() condition require ( one or many ) seek on the index ( except for the deleted() condition ).
>and the Status Table can to be ignored.
>
>SQL Server works so, but it seems me strange that VFP has these optimizations.
>
>compare the INNER with the LEFT JOIN

Thanks, I have workarounded the issue by adding an additional field in the main table, avoiding by the same the use of the inner join which was not necessarily fully optimizable in such circumstance. When comes time to deal with big tables, sometimes, such a design is worthwhile.