>I use p-views when using tables of 20,000 or more records. The largest table now has more than 100,000 records, and I have no problems.
>
>The key is to show only a small subset of the data, and to optimize the view. I do not mean Full Rushmore Optimization - partial optimization is often faster (see my FAQ on Rushmore, for details).
>
>I don't even consider 100,000 records as "large" - for VFP, and today's computers, that would be medium, at most.
>
>OTOH, a filter is very slow if used with a grid.
>
Thanks for the feedback, Hilmar. I suspected as much. And I realize 100,000 records is not really "large" by VFP standards, just large for me and my experience.

How do you handle indexing your p-views? I want to maintain the incremental search and grid header click to set table/view order.