Ron,
This is a buffering issue. SQL selects open source tables/views again in new work areas. This is done to protect record position. Because of this, the view is reopened and the delete has not taken place yet. When you save the deletion, it gets written to the source tables and the select sees that it is deleted.

To avoid this, you can use xBase commands that work on the memory presence of the table/view. Use SCAN...ENDSCAN or LOCATE...CONTINUE and SEEK() to check values prior to saving.

HTH.

>Larry,
>
>I have played around with the deleted() as well. Even if I set the "set deleted" I always get the same result from my view. Although the deleted records are NOT shown when browsing the view they do show up when asking for the 'duplicates'.
>What I have done now is to ask the question after saving the data and then the query is returning the proper results from the view.
>Personally I don't like this because I want to do this before saving, not after saving.....
>
>Thanks,
>Ron