Cerebrus, In looking at it it makes perfect sense now. I think I just got caught up in OOP and was focusing on the object (which of course was only created through the reference variable.) Where I created the reference VARIABLE is where it will have scope. Just realizing that I was still dealing with a VARIABLE got my head where it needs to be. I do know the scope of variables, again I just became focused on this shiny new thing called Objects that I forgot to look at the whole process. Your advice was dead on, thanks for still leaving it for me to solve and not just solving it for me. Did you eve notice that epiphanys are so much cooler when they are your own!
On Nov 13, 2:08 am, Cerebrus <[email protected]> wrote: > Nothing to be embarassed or ridiculed about. IMHO, people who deserve > to be ridiculed are not those who do not know something, but those who > do not know something, are afraid to ask and expect others to help > them without investing the slightest effort to learn themselves. > > You should research "variable scope", not object scope. In the sample > you posted, the variable "Greg" is declared within the Form Load > eventhandler and is therefore not available in the Button click > eventhandler. Make it global and it will be available throughout the > class.
