>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?

Yes, It works like a SET FILTER, and we simply can't avoid the SET DELETE ON issue. You've got a point up here.

>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


In many cases, it does not make any difference. Only in very particular cases (COUNT FOR, Filtered SQL queries, and tables which contain lots of deleted records) and index might help to improve performance. Generally it doesn't help (much) and could only burden performance. There seems to be an FPA article about this issue, though I've never read it.

Walter,