Using MDIParent forms in vb.net

Question

1.00/5 (1 vote)

See more:

Hi,
I have inserted an MDIParent form in my project. There is a datagridview on it. When I add data to it (on parent form) and then open a child form through Parnet form, it displays the datagridview, which it should but there are two unwanted things:

1) It also takes all the data which I entered on Parent form's datagrid view

2) When I make change to data on child form, the effect also transfers to the parent form's datagridview.

Please advise how to make controls on parent forms the data changes of which limit to the current form only, not on all children and parent forms.
Thanks

[edit]unnecessary code block removed[/edit]

Posted 17-Jun-13 0:01am

Furqan Sehgal

Updated 17-Jun-13 0:30am

Nelek

v2

Add a Solution

Comments

Simon_Whale 17-Jun-13 6:39am

how are you connecting the data to the grids? are they sharing a variable etc?

Furqan Sehgal 17-Jun-13 7:15am

I just tired it adding data directly from the keyboard

PrissySC 18-Jun-13 18:16pm

Are you using a common bindingsource for each data grid? If so, they will bind to the bindingsource and changes made to the bindingsource are what the grids both will display. Two bindingsources will stop this, but if you need to link the data you will have to consider how to handle the datamembers or make updates if needed to the child or parent grid.

2 solutions

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Sergey Alexandrovich Kryukov · Answer 1 · 2013-08-06T08:15:00

Here is the idea: who needs MDI, ever? Why torturing yourself and scaring off your users?
Do yourself a great favor: do not use MDI at all. You can do much easier to implement design without it, with much better quality. MDI is highly discouraged even by Microsoft, in fact, Microsoft dropped it out of WPF and will hardly support it. More importantly, you will scare off all your users if you use MDI. Just don't. Please see:
http://en.wikipedia.org/wiki/Multiple_document_interface#Disadvantages[^],
How to Create MDI Parent Window in WPF?[^].

I can explain what to do instead. Please see my past answers:
How to Create MDI Parent Window in WPF? [Solution 2],
Question on using MDI windows in WPF[^],
MDIContainer giving error[^],
How to set child forms maximized, last childform minimized[^].

—SA

BCD23 · Answer 2 · 2013-06-20T23:48:00

Solution 1

Use different binding source. If u r using same binding source then this problem can arise. When you update any of the grid then the common table adapter gets filled (updated) and so u r getting effects in both of grids.

Posted 20-Jun-13 23:48pm

BCD23