How pass variable from one form to the next in Win app?

[Ronald S. Cook]

I have a form open and when a user clicks a button I do a frmNew.Show() and
this.Hide. But I have a value that I need to pass to the new form. How can
I do this, please?

Thanks very much,
Ron

[Tim Wilson]

There are a few ways to do this. Here are a couple that come to mind.
(1) Create a property exposed from the second form and push the value into
this property before showing the form.
(2) Create a constructor overload for the second form and pass the value in
when creating the instance of the form.

--
Tim Wilson
..NET Compact Framework MVP

"Ronald S. Cook" <rc***@westinis.com> wrote in message
news:eI**************@TK2MSFTNGP11.phx.gbl...

I have a form open and when a user clicks a button I do a frmNew.Show() and this.Hide. But I have a value that I need to pass to the new form. How can I do this, please?

Thanks very much,
Ron

[Michael Nemtsev]

Hello Ronald,

Create Singleton object, where keep you data (like Cache), and use in from
different forms

RC> I have a form open and when a user clicks a button I do a
RC> frmNew.Show() and this.Hide. But I have a value that I need to pass
RC> to the new form. How can I do this, please?
RC>
RC> Thanks very much,
RC> Ron
---
WBR,
Michael Nemtsev :: blog: http://spaces.msn.com/laflour

"At times one remains faithful to a cause only because its opponents do not
cease to be insipid." (c) Friedrich Nietzsche

[Jon Skeet [C# MVP]]

Michael Nemtsev <ne*****@msn.com> wrote:

Create Singleton object, where keep you data (like Cache), and use in from
different forms

Unless the value really *is* a logical singleton, I'd advise against
using a singleton to store it. We don't use singletons to store all
data that needs to flow between other objects - why should forms be any
different? I'd go with Tim's answer.

I often find it interesting how many questions come up about forms
which suggest that people think of them in a totally different way to
other classes. I wonder whether it's the designer aspect of things -
perhaps if people wrote forms from scratch, they wouldn't make as much
mental distinction between them.

--
Jon Skeet - <sk***@pobox.com>
http://www.pobox.com/~skeet Blog: http://www.msmvps.com/jon.skeet
If replying to the group, please do not mail me too

[Michael Nemtsev]

Hello Jon Skeet [C# MVP],

J> Michael Nemtsev <ne*****@msn.com> wrote:
J>

Create Singleton object, where keep you data (like Cache), and use in
from different forms

J> Unless the value really *is* a logical singleton, I'd advise against
J> using a singleton to store it. We don't use singletons to store all
J> data that needs to flow between other objects - why should forms be
J> any different? I'd go with Tim's answer.

Agree, but it depends on app. For example in one day we can end up that we
need to give web access to our app and to show this data.
I just gave more abstract solution, but again, w/out knowing more about data
we can't predict where and how it will be used
---
WBR,
Michael Nemtsev :: blog: http://spaces.msn.com/laflour

"At times one remains faithful to a cause only because its opponents do not
cease to be insipid." (c) Friedrich Nietzsche