>> I snipped this because it was getting too long to scroll down to the new statements. Maybe we could all do this?
>>So, you retrieve recordset by SQL, then index it (or you have index on view?) and use SEEK within it? It seems to me as double work.
>
>Ed,
>
>This is not double work, it is using a design approach that is scalable as opposed to one that is not scalable. I also use SELECT or P-Views to narrow down the record set and then will use seek within the VFP code to manuver within the sacled down record set. It is not double work and it is scalable, all I ahve to do is give the views a remote source and none of my code has to change, it all works in either situation.

So you want to say that you never use SEEK against base tables?
Answer this question, please.

I understand that it's scalable, but it's still double work that takes performance hit.