>>>>With NOFILTER (and deleted still off), yes, all records are returned and the deleted flag is wiped regardless of any other setting.
>>>>
>>>>What I haven't tested yet is whether or not it speeds up the query. That's my next step.
>>>>
>>>I have skipped most of the thread so pls forgive if I am totally off target:
>>>Since you seem to use SQL-Select, would not something like
>>>Select *, deleted() as lWasdeletd from ...
>>>fill your need the keep the info on the deleted() status of the base table for your next steps ?
>>>
>>>regards
>>>
>>>thomas
>>
>>Interesting idea. Hadn't thought of that, I must admit. Anything is worth trying
>>
>>Thanks
>
>Not to be pesky, but I did suggest it in my first message to you <g> I called the field lDeleted, though <g>

By golly, yes, you did. I guess that because I thought, at the time, that I didn't need to worry about it, I wasn't paying enough attention. In fact, last night when I read Thomas' message, again, I didn't pay much attention. It was only this morning when I discovered that using functions or adding temporary fields to the select would wipe out the deleted flag that I knew I had a bigger problem than I thought, and I guess Thomas' message was fresher in my memory.

Had I known then what I know now, this thread would have been a whole lot shorter after your initial message. Anyway, that appears to be the answer. I've changed my code in a number of places now, and it works beautifully.

In fact, even if I run into a situation of joining 2 tables, then I can use the same process but it will just require one or two more steps and intermediate cursors. I tried it out in test this morning and it is still fast, even with more steps.

Ya really gotta love this UT place.

Thanks for everything Naomi.