Call userform control click event indirectly

Try the Application.Run method.

command buttons are easy because you can use the .Value property to fire the click event. Not so fore Labels.

You would need to move the contents of the event code to separate routine in a standard code module. Then you can implement shg's suggestion of using the run method

Thank for jumping in, Andy, Kyle, and nice suggestions. Ryan, I leave you in the hands of two smarter guys.

Kyle, that would require that you use the default instance of the userform without some additional qualification, correct?

shg, your too modest.

Here is an example using both approaches.

@ Kyle: Ah, the CallByName code is in the form. I missed the Me.

@ Andy, thank you for the examples.

Still not entirely grokking, though. Why is it necessary to make the subs public if the code is in the same module? What's the downside to making them public?

There isn't really a downside in this case, but generally it's better encapsulation to keep as much private as possible and only expose the bare minimum of methods/props/functions required to perform the role of the object, this solution is a bit of a hack.

There should be no real need to expose the Label_Click since all its interaction is really done within the form, it's not nice to have outside influences fiddling with it

CallbyName will only work on public methods since you can't call private methods from outside the object. CallByName is called from outside the object and thus has no access to private members

CallbyName will only work on public methods since you can't call private methods from outside the object.

That makes sense, I think ...

I've used CallByName maybe twice in my life. I need to write that down someplace.

Thanks, Kyle.

Is it me or is the help on CallByName for VB6 rather than VBA?

It's certainly obscure.
The help suggests you can pass the control as the object, but the Form_Load event and Move method on a button suggests it's not VBA