>>Chapter 3 from Nightmare on VFP Street?
>>
>
>It's just an attempt to get the code to stay alive during the removal; since things are Destroyed inside out, the child button has to be released before the parent container, so where does VFP pass control when the RemoveObject is done if the context is no longer valid...
>

I understood the reasoning, I was just commenting on your interesting choice of object names (txtAssassin, oParentOfCondemned) - logical, but very interesting :)