>>Oops, that was a false memory. That happened in my addactivate method which is called by my baseclass form's Activate. This method call is from within a WITH/ENDWITH. I thought that was somewhat bizarre behaviour at the time and changed it when I found it -- just in case MS decides to fix it in future versions.
>>
>
>I don't think they'll change it. It's a pretty well known "feature".

I don't like this feature because you always have to remember that such methods have to be called within a WITH/ENDWITH. This leaves any such methods wide open to generating errors if not called in such a manner.