Mark,

This is probably a dumb question but what is the

I have notice other type of the in responses and
am not sure of the meaning.
-myron kirby-
===============================
>>>Erik:
>>>
>>>Dragan is fairly correct in that this is the behaviour I observe. However, to overcome the problems, I have had to eliminate the delete column and add a delete button. When you click the little delete square, the deleted() method fires, but the actual delete of the record does not occur until after the method completes. I have tried DoDefault(), etc., including deleting the record number passed to the method. What then shows on the grid, when I issue a delete, are 2 deleted records -- the one I deleted and the next or previous record. The behaviour is totally unpredictable (at least to me).
>>>
>>>However, I did not use Dragan's exact suggestion, which I will try (I left off the nodefault at the end):
>>>
>>>dodefault()
>>>do_my_code_here
>>>nodefault
>>
>>It looks like you can issue nodefault and then delete the record yourself. Works for me.
>
>Yes it does. What finally worked perfectly was

>   parameter nRecNo
>   delete record nRecNo in MyTable
>   run.my.code.here()
>   nodefault

>I purposely left out DoDefault() because I can't imagine ever having default code in the original sub-class, at least not in this method.