>>All it does is called the code in event w/o triggering event, which is not a good idea in the first place. See >http://fox.wikis.com/wc.dll?Wiki~MethodsShouldNeverCallEvents
>
>I disagree with this theory -- methods can not call or trigger an event. Events trigger methods. The Click() code contained in an object (form, control, etc) is not the event -- it is the method code called as a result of the event. Calling one object's Click() code from another object's method code is no different than calling a custom named method. The actual event (in this case, button click) is not raised by one method calling the click() code.

It's you own theory that method cannot call an event. It certanly can.
Again, a method can trigger an event by using RAISEVENT() function but not by calling code bihand it.
However a method shouldn't call an event code for reasons explained in the wiki article.