>This way we handle the deletion ourselves. Deleting two records instead of one.... hmm, it's kind of contradictory; as if there was some Set Deleted On/Off swapping during the method execution (both the default and/or custom).

I had set deleted on, issued a delete in the method, did not have nodefault, so when the method code ended, it issued its own delete on the currently selected record which was the record after the one I clicked on.

>Made myself smile for a moment: instead of "if deleted()... recall... else... delete... endif" I started typing "this.deleted=!this.deleted". An unintentional prophecy?

LOL :) I have done that too [this.deleted()] in actual code. Took me more time than I care to admit to figure out what I did.