That means there is no code "wiring-up" the event handler. If you're looking at the position of Form2 from inside Form1 code, you have to "wire up" the event yourself. If you're only looking at the position of Form2 inside Form2 code, the event isn't getting wired up in the Designer code. Which is it? Asking questions is a skill CodeProject Forum Guidelines Google: C# How to debug code Seriously, go read these articles. Dave Kreskowiak

Does the sender object not pass through? It seems to me you should be able to ID the sender inside the delegate and work from that side of the problem. Use one delegate for all of the inputs, that delegate checks the sender ID and matches it to a function based on it's MapTo setting. I forget if you can create a collection of functions in VB.Net, but even without it, that should at least cut the list down to one look up for the MapTo and a 25 option select statement. The true man wants two things: danger and play. For that reason he wants woman, as the most dangerous plaything.

First of all, you should not use a structure for this, you should use a class. A structure should not be larger than 16 bytes, and you break this if you have more than four string references. Also structures are tricker than classes to implement correctly. If you want a fast lookup for a field you can create a Dictionary with the field as key and the object as value. Despite everything, the person most likely to be fooling you next is yourself.

I think that's a very good solution. I've used that system a lot. The only thing is that you may consider running the replace twice. First put the variables in place and then format the string with newlines. I sometimes have strings in variables that also contain \n. Doing this in two phases also replaces the newlines from variables correctly. The need to optimize rises from a bad design.My articles[^]

Thanks - that makes sense ;)

Georg Kohler wrote: Thanks - you guys are great! I knew there had to be a simple solution .... You're welcome. Best place to look first is always the documentation. :) Scott Dorman Microsoft® MVP - Visual C# | MCPD President - Tampa Bay IASA [Blog][Articles][Forum Guidelines] Hey, hey, hey. Don't be mean. We don't have to be mean because, remember, no matter where you go, there you are. - Buckaroo Banzai

You're welcome. Glad it going you heading in the right direction. Scott Dorman Microsoft® MVP - Visual C# | MCPD President - Tampa Bay IASA [Blog][Articles][Forum Guidelines] Hey, hey, hey. Don't be mean. We don't have to be mean because, remember, no matter where you go, there you are. - Buckaroo Banzai

Assume Main is a form and not another module/class/object Are you passing an instance of "Main" to your module. EG calling the function in your module from the main form dim oModule as new Module oModule.CallFunction(me) Public sub CallFunction(oFrm as Form) oFrm.Drivenabled=true end Sub Never underestimate the power of human stupidity RAH

I'm not sure if I'm getting this ... Am i correct in that Interfaces are intended to be used for code that's exactly the same ? Public Interface ITest Sub test() End Interface Itest will be the same in both controllerA & controllerB If this is how it works that that's NOT what I need I have a user Interface that will call the subs inside to different classes, ControllerA or ControllerB (The SUB NAMES Inside the classes are identical but the code inside the subs will never be!) I believe it would make my live a lot easier (and Cleaner to maintain ) if I could just call the "same" subs out of my user interface Sub Jog_X() SelectedController.jogging ' where SelectedControler.Jog_X will have to point to 'A) ControllerA.Jog_X 'or 'B) ControlerB.Jog_X end sub Georg