Todd,
Have you tried changing the order of the tables in the JOIN clause. That sometimes helps. If that doesn't help, play with using the FORCE keyword in the select statement. VFP may still be trying to do something with the order of the tables and FORCE keyword will make it use the order you specify.

HTH.

>I know this has been posted already but I am still looking for answers.
>
>Assume the following table:
>PLOTS: 300K records and the possibility of 1.5M records. Index on field "plot_id".
>
>cFilter: 1 TO RECCOUNT("plots") records. Index on field "linkfield"
>
>View appear to be a great tool when used with a simple where.
>
>

WHERE plot_id = ?lnPlotId)

>
>The abopve returns one record. No more, no less. And in under .01 seconds.
>
>But what if your WHERE isn't quite so simple?
>

WHERE plot_id IN (SELECT linkfield FROM cFilter)

>OR
>

WHERE EXITS (SELECT linkfield FROM cFilter)

>OR even change the WHERE to a JOIN
>

JOIN cFilter ON plots.plot_id = cFilter.linkfield

>
>Select times can run up to 20 minutes in a logrithmic type curve.
>
>SET DELETED is OFF
>All indexes appear proper.
>SYS(3045,11) indicates that rushmore if full when it should be (example #1) and none in examples 2 and 3. On example 4, SYS(3045,11) returns joining table x to table y on index z.
>
>Anyone have any thoughts?
>
>TC