>>I have a parameterized view (that I created when my knowledge of vfp was less than it is now..thats scary), with a filter option of "deleted() # .t.". This view is being used in an environment where set deleted is on. The base table does not have an index on deleted(). The view only retrieves a few records but is extremely slow over a network (3 or 4 seconds).
>>
>>Am I right in thinking that there is no need for the filter option of "deleted() # .t." since my set deleted is on?
>>
>>Thanks for any input
>>
>>Paul
>
>If you use the DELETED ON, then you should have an index on DELETED() as it would speed things up. My opinion anyway.

Bret,

That is actually what I thought about doing first...and when I do create an index on DELETED() it DOES improve performance significantly. However, I spent a lot of time reading threads on this very subject yesterday and came to the conclusion that I probably shouldn't use index tags on DELETED().

So, after a lot of testing the only way I could get good performance without the index on DELETED() was to remove the DELETED() # .t. filter and got to thinking that maybe it doesn't make sense to have that filter anyway...