Hi Mike,

>This stuff about SET FILTER got me wondering last night how SET DELETED ON works. I figured that it is really an internal SET FILTER. Does anyone now for sure? If the case, should you avoid SET DELETED ON? Wouldn't that slow it down abit?

Phew, and again. :)

Yes, SET DELETED ON is an internal filter, just like SET FILTER. It is evaluated like any other filter. This means, VFP first tries to optimize it via Rushmore (if SET OPTIMIZE is ON) and if that doesn't work, evaluates every record against this expression. If SET DELETED can't be resolved with Rushmore, it's evaluated after all optimizable expressions have been applied, ie. against the result set created by optimizable expressions.

>And without starting another thread, what is the final desicion on the DELETED() index expression, does that speed up SET DELETED ON?.

It does for count operations and filtered cursors, but nothing else.

Christof