Cableguy Expert Licensed User Longtime User Jan 4, 2009 #1 This as been talked about in "Q&A" but although the can workaround it, The ability of using an event in another module that NOT the owner of the control/Object would be usefull Like we do for properties: Main.TextBox1.Text="" we could use: Main.TextBox1_GotFocus
This as been talked about in "Q&A" but although the can workaround it, The ability of using an event in another module that NOT the owner of the control/Object would be usefull Like we do for properties: Main.TextBox1.Text="" we could use: Main.TextBox1_GotFocus
agraham Expert Licensed User Longtime User Jan 4, 2009 #2 Maybe I am missing something but I'm afraid that I don't understand the problem AddEvent("Module1.Button1", Click, "Main.Button1Click") Works when Button1 is on a Form belonging to module "Module1" and the event Sub "Button1Click" is defined in Module "Main".
Maybe I am missing something but I'm afraid that I don't understand the problem AddEvent("Module1.Button1", Click, "Main.Button1Click") Works when Button1 is on a Form belonging to module "Module1" and the event Sub "Button1Click" is defined in Module "Main".
Cableguy Expert Licensed User Longtime User Jan 4, 2009 #3 Its an extra line of code, and if missplace can result in app errors... Most of my modules DONT need a globals Sub, so I got rid of it... It just would be simpler to use...
Its an extra line of code, and if missplace can result in app errors... Most of my modules DONT need a globals Sub, so I got rid of it... It just would be simpler to use...