Seth,
Don't know. But why not just call the procedure that handles the click
directly?
One of the biggest reasons I don't call & don't recommend calling the
procedure directly is that there may be multiple handlers for the event.
By calling the handlers directly you are coupling that code to the handlers
themselves. By calling PerformClick you are only coupled to the button
itself. The number of handlers is immaterial...
--
Hope this helps
Jay B. Harlow
..NET Application Architect, Enthusiast, & Evangelist
T.S. Bradley -
http://www.tsbradley.net
"rowe_newsgroups" <ro********@yahoo.comwrote in message
news:11**********************@k70g2000cwa.googlegr oups.com...
Don't know. But why not just call the procedure that handles the click
directly?
i.e.
<pseudocode>
Form.Visible = False
Button1_Click(me, eventargs.empty)
</pseodocode>
Thanks,
Seth Rowe
st***********@hotmail.com wrote:
>Form.Visible=False
Button1.PerformClick
It does not fire the Button1.Click event.
Why?