Re: Reload a opened form another form - C# Discussion Boards

Martin#19-Jul-07 22:33

19-Jul-07 22:33

Nisha S. wrote:
This is my first message to this forum

Wellcome!

Nisha S. wrote:
I need to reload the first form with the added record before closing the second

I would use the ShowDialog() method to show the second form modal.
This will allow you to reload the datas in the mainform, when the method finished (second Form closes)

If you have to use Show(), you would need to handle the Closeing or Closed event of the second form.

Hope it helps!

All the best,

Martin

N a v a n e e t h19-Jul-07 22:35

N a v a n e e t h

19-Jul-07 22:35

Simple method. But I don't know how much efficient is this when considering about big applications. What you can do is pass first forms object to second form when second from loads. Make datagrid to public. Using first forms object you can access datagrid. Bind that as you do always

My Website | Ask smart questions

Pete O'Hanlon19-Jul-07 23:13

19-Jul-07 23:13

No - you don't do this. This violates so many OO principles that I don't know where to begin. Please don't recommend behaviour like this.

Deja View - the feeling that you've seen this post before.

Sathesh Sakthivel19-Jul-07 22:49

Sathesh Sakthivel

19-Jul-07 22:49

Nisha S. wrote:
This is my first message to this forum.

Welcome to CP.

Nisha S. wrote:
I beleive you guys are very helpful.

We are here to Help you.

Just try by using Crosspage Post back method.

SSK.

Pete O'Hanlon19-Jul-07 23:00

19-Jul-07 23:00

What? What on earth is the "Crosspage Post back method"? If you want to help, provide an explanation of what this is.

Deja View - the feeling that you've seen this post before.

J4amieC20-Jul-07 0:12

J4amieC

20-Jul-07 0:12

Satips please at least confine your rubbish to Lounge/Soap Box

---

How to get answers to your questions[^]

T.EDY19-Jul-07 22:55

19-Jul-07 22:55

use the Form2.ShowDialog() better than Form2.Show()
it should answer your question

Regard,

TCim

Pete O'Hanlon19-Jul-07 23:02

19-Jul-07 23:02

Please tell me that you don't use default names. Tell me that you are using Form2 as an example only.

It is never good practice to leave default names for something - what is the purpose of Form2? Can you tell without opening the form up and having a look?

Deja View - the feeling that you've seen this post before.

T.EDY19-Jul-07 23:11

19-Jul-07 23:11

i used form2 only for the example..i know that is bad naming if we use Form2 or Form1 for naming a form Smile | :)

Pete O'Hanlon19-Jul-07 23:14

19-Jul-07 23:14

That's OK then - now, lets make sure that the OP knows not to do this. Smile | :)

Deja View - the feeling that you've seen this post before.

Martin#19-Jul-07 23:33

19-Jul-07 23:33

Pete O`Hanlon wrote:
It is never good practice to leave default names for something - what is the purpose of Form2? Can you tell without opening the form up and having a look?

Pete O`Hanlon wrote:
Tell me that you are using Form2 as an example only.

Which is actually a bad one, cause it would make the beginners think, that they would not need an instance of the form (which is per default named "Form2" as class name) to call ShowDialog.
And then will ask 10 min. later why they get a compile error.

All the best,

Martin

T.EDY19-Jul-07 23:09

19-Jul-07 23:09

try use Form2.ShowDialog()
then you'll not have to set your first form to show after second form is closed

Regards,

TCim

Martin#19-Jul-07 23:22

19-Jul-07 23:22

What are you doing here?

P.S.: and agian "Form2"

All the best,

Martin

T.EDY19-Jul-07 23:47

19-Jul-07 23:47

i'm sorry .. Form2 just an example, not the name of the form

Regards,

TCim

Martin#19-Jul-07 23:49

19-Jul-07 23:49

OK, ok,
But why are you posting same answere twice?

All the best,

Martin

T.EDY20-Jul-07 0:09

20-Jul-07 0:09

First i post a message..my post doesn't show in forum then i posted it again, then i get my new and old message show

Regard,

TCim

Pete O'Hanlon19-Jul-07 23:11

19-Jul-07 23:11

As Martin stated, you should use the ShowDialog method. Then, depending on the DialogResult from the form, you would reload the data (as it doesn't make sense to reload the data if you haven't actually done the save).

Suppose that you have a form called OptionsDialog which you are going to use to add some options into a program and that the details will be saved to the database when the user clicks OK. In this form, set the DialogResult of the OK button to OK.

In your parent form, you would call it with something like this:

private void AddOptions()
{
  using (OptionsDialog dlg = new OptionsDialog())
  {
    if (dlg.ShowDialog(this) == DialogResult.OK)
    {
      ReloadOptions();
    }
  }
}

I hope that this helps.

Deja View - the feeling that you've seen this post before.

N a v a n e e t h19-Jul-07 23:31

N a v a n e e t h

19-Jul-07 23:31

Good. My 5. But please make me clear on this

Pete O`Hanlon wrote:
using (OptionsDialog dlg = new OptionsDialog())

What is this statement ?

How about using delegates to get the same result ? is it a good practice ?

My Website | Ask smart questions

Martin#19-Jul-07 23:54

19-Jul-07 23:54

N a v a n e e t h wrote:
Pete O`Hanlon wrote:
using (OptionsDialog dlg = new OptionsDialog())

What is this statement ?

A "using"-block will Dispose and Close the form automatically after code block has finished!
So you don't have to worry for that.

N a v a n e e t h wrote:
How about using delegates to get the same result ? is it a good practice ?

It depends of the problem and the way something has to be solfed.
In this case it would be neccesary if the programmer says, that ShowDialog should not be used (maybe because of aditional parallel interaction with an other form).
Than you would have to use Show(), and Form provides the delegates for that (Close and Closing)

All the best,

Martin

Pete O'Hanlon19-Jul-07 23:59

19-Jul-07 23:59

The using statement here means that I don't have to remember to call the Dispose() method on the form. Another way to do this would be:

OptionsDialog dlg = new OptionsDialog()
try
{
  if (dlg.ShowDialog() == DialogResult.OK)
  {
    ReloadData();
  }
}
finally
{
  dlg.Dispose();
}

The C# team provided the using command as a shortcut so that any type that implemented IDisposable could be automatically disposed. This feature was added to VB.NET in .NET2.

Using delegates is also a good way to do this, especially if you don't want to go the ShowDialog route. Suppose that you have a modeless dialog, delegates are a very good way to pass the information back.

Deja View - the feeling that you've seen this post before.

N a v a n e e t h20-Jul-07 1:21

N a v a n e e t h

20-Jul-07 1:21

Thanks pete for making concept clear.

My Website | Ask smart questions

Pete O'Hanlon20-Jul-07 1:46