Heresy ?

[Barret Bonden]

Heresy ?

I successfully and simply passed data from one form to another. (this
after days of frustration at the methods I read of and that felt to me to be
verbose and over exact)

I created a public variable with :

Public shared v as string (shared being the key, I suspect)

And on another form having created a copy of the first (with the variable v
in it)

Dim f2 as new form1

Textbox1.text=f2.v

Have I committed heresy ? Am I bound for OO purgatory ? Or if not a symbolic
(NPI) crime, are there any real negative ramifications to using such
variables commonly ?

[Herfried K. Wagner [MVP]]

"Barret Bonden" <ar****@networks-cc.com> schrieb:

Heresy ?
?!?
I successfully and simply passed data from one form to another. (this
after days of frustration at the methods I read of and that felt to me to
be
verbose and over exact)

I created a public variable with :

Public shared v as string (shared being the key, I suspect)

You'll ger into trouble if there is more than one instance of the form and
each of the instances should have its own 'v'. Instead of using a shared
variable a public property of the form + passing references to form
instances might be the preferred way.

--
M S Herfried K. Wagner
M V P <URL:http://dotnet.mvps.org/>
V B <URL:http://dotnet.mvps.org/dotnet/faqs/>

[gregory_may]

If your trying to get information OUT of a form, you may want to look at
RAiSEEVENT. Your other form can subscribe to the event & it wont cause
heart aches if you have multiple instances of publishers & subscribers.
http://msdn.microsoft.com/library/de...RaiseEvent.asp
"Barret Bonden" <ar****@networks-cc.com> wrote in message
news:30*************@uni-berlin.de...

Heresy ?

I successfully and simply passed data from one form to another. (this
after days of frustration at the methods I read of and that felt to me to
be
verbose and over exact)

I created a public variable with :

Public shared v as string (shared being the key, I suspect)

And on another form having created a copy of the first (with the variable
v
in it)

Dim f2 as new form1

Textbox1.text=f2.v

Have I committed heresy ? Am I bound for OO purgatory ? Or if not a
symbolic
(NPI) crime, are there any real negative ramifications to using such
variables commonly ?

[Todd Bandrowsky]

> Have I committed heresy ? Am I bound for OO purgatory ? Or if not a symbolic

(NPI) crime, are there any real negative ramifications to using such
variables commonly ?

Well, you are going straight to hell actually. The right thing to do
is to create your own class that has data that may be shared among
multiple forms. Instantiate that object when your application first
starts and have it live as a static. As an added benefit, you can do
groovy things like have multiple different forms pointing at the same
data, and changing it. If you build in a good event handling
mechanism, then you can have all of your forms updating when you
change on form.