Dragan,

I knew you knew all that, I was just posting for Mark's benefit.

>Right... I thought of that, but .SendMessageToUT() fires earlier than that in the regular event loop :). Such a control would have to be disabled, or .tabstop=.f. or to return .f. from its .when() - it needs to be not just out of the picture, but out of the loop as well.
>
>Having to remove a control in such a way is a kludge per se to start with. Any other trouble just naturally follows from that :).
>
>I think I had only one such case where I couldn't rework the class and had to remove an object - and it was a page. Setting it to disabled, invisible or whatever worked only partially: it would be just disabled, but wouldn't go away. Returning .f. from its .init() was the only way. I was just lucky that the page was coded as optional, i.e. not referenced in any way elsewhere, so no bad thing happened.