>>>>>>>Can anyone tell me whether SELECT - SQL respects SET DELETED ON/OFF? I used to know this.
>>>>>>>
>>>>>>>thank you
>>>>>>
>>>>>>Yes, it respects it in all reasonable situations. The only exception if you run SELECT * From Table INTO Cursor, and even this case can be remedied by NOFILTER.
>>>>>
>>>>>Thanks, Edward,
>>>>>
>>>>>The problem I appear to be having is that SELECT is selecting deleted records when SET DELETED is ON -- puzzling!
>>>>>
>>>>>regards
>>>>
>>>>That's strange. Are all tables open before SELECT? Also, if you SELECT into cursor, try NOFILTER.
>>>
>>>Edward,
>>>
>>>I think all tables are open -- I guess I assumed they are since I'm getting no error messgages to that effect -- but I guess I'd better check.
>>>
>>>Thanks again,
>>>
>>>regards,
>>
>>James, is there any chance you're in a private datasession? The value of SET DELETED is scoped to the current data session.
>
>Rick,
>
>I'll bet that's it. I used to as a routine matter code a "where ... !(DELETED()) into all Selects, and I cannot imagine why I stopped. Back to the old ways, eh?
>

Don't return back, this way you just cannot use joins.