Fabio
Good try but no cigar. Swapping table positions in the join from propnum=pocontact to pocontact=propnum did not return results expected.
The new index on groupid did mot change speed. The browse is taking 5.84 now instead of 5.67sec before. I could figure out how you got the FORCE in the query since I used the query builder for the views. I did it from command window but no difference in speed.
good ideas but frustrating!
>Hi,
>
>i need other info, but...
>
>***********
>remove order because it in not optimizable ( add it after ) and try this:
>
>* need a index on Pocontact.memoid
>SELECT *;
> FROM FORCE property!propnum LEFT OUTER JOIN property!pocontact ;
> ON Pocontact.memoid = Propnum.contactid;
> WHERE LEFT(Propnum.groupid,2) == "PN"
>* a index on LEFT(Propnum.groupid,2) is usefull also
>
>*************
>post: RECCOUNT(property!propnum) and RECCOUNT(property!pocontact)
>*************
>This is a remote view on a VFP ODBC ?
>I donnot use this, for now, and i haven't big experience for get max optimization.
>
>Fabio
Extreme Programming = Plan -> Design -> Code -> Test