>>It is not supposed to be showing when Set("Deleted")="ON". With off, everything shows. Also, the scope of the settings is "all aliases in the current data session", not per table.
>>

>Well when buffering mode is on PEssimistic. even if set deleted is On it does get deleted but "Comes back" when the form is loaded again. but buffering mode 0 seemed to take care of that.

Buffering 0 means you write directly to the table - no way to undo if user clicks Cancel (and they expect to have a functional cancel button for the last 20 years). With table buffering, it isn't written into the table until you explicitly call tableupdate() for each table in need of salvation. With row buffering, it is updated when you move the record pointer in that table, when it calls tableupdate() behind your back. So if it comes back, it means the change in the buffer didn't get written into the source table on disk.