>Hi Folks,
>
>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?

Mike,

I can't speak for anyone else, but I have not said that SET FILTER is somehow something that should NEVER be used. I ahve said it is commonly misused which is quite a different statement.

As for set deleted, it can be on or off as far I am concerned depending on the requirements. It is the way VFPO data works. If youa re using netive VFP tables and there is the possibility of deleted recors adn you want them ignored you either filter them yourself somehow or you set deleted on.

>And without starting another thread, what is the final desicion on the DELETED() index expression, does that speed up SET DELETED ON?. IMO, this should be another document, because there are plenty of long (confusing, and difficult to read) threads on it

I don't think anyone can give you a final answer on this issue. In smaller data sets using the deleted index still makes things go faster. In very large data sets it can have teh exact opposite effect. So, the final conclusion is to test test test and then decide how to do things. For me, this simply means that the deleted index is no longer an automatic good thing to do but requires that I consider the ultimate data file sizes.