>>Thanks for the reply! I don't have Design Patterns, but I think you're advocating basically what I ended up doing anyway ...
>>
>>

>>*-- MarkDeleted() method
>>IF THISFORM.OtherObject.DelMethod('CheckIt')
>>  DODEFAULT()
>>  THISFORM.OtherObject.DelMethod('DidIt')
>>ENDIF
>>

>>It works fine, and now that I think about it, it's not all that inelegant a solution.
>>
>>Bonnie
>
>Nope... not what I am saying at all... What I am saying is, break the DelMethod into two methods... and one would call the other... So, when you call the method from the other form, it doesn't have the code in it that you don't want to execute, so you don't have to call the parent code from the other form.
>
>BOb

Well, Bob, looks like we're going around in circles here. I'm still not sure what you're saying. What's wrong with having two calls to the DelMethod() with different parameters. The reason I like doing it this way is because all the functionality is in one method. I dunno ... it makes sense to me. < g >

Bonnie