Hi Aaron
This is strictly from the for what its worth department, because I'm not
sure I follow completely, but the behavior you describe in 1-4 seems to
me to be by design. ie. If you code an event, you have to tell the event
handler that the procedure exists by clicking on the v and selecting
[Event Procedure] Or... you let it know first by clicking on the
build-type button at the right of the selected event field. In other
words, coding manually isn't preventing it from firing, not telling it
to use the [Event Procedure] is. As for the third party control, some
such controls don't have events which appear like the normal OnClick,
etc. via the Properties and instead are addressed using something like
CommDlg.ShowOpen or Lead.FreeRegion.
Well, like I said... for what its worth
Stan

when switching to code window try opening the left object combo and choose your
new control. then open the right combo and have a look at the events. you'll
probably find there all events of the control. I faced the same problem with ms
treeview control.

cu Steffen