[RESOLVED] Recommendations for handling forms

[derohanes]

I'd like to get some guidance on how to structure my application. Basically I have a main form that leads to another form that adds something to a database and returns to the main form. The overall question is, do I use a MDI structure or just do as I am doing now, which is using .show and .hide on the various subforms. I started this application as an SDI. Here are the questions.

1. What are the advantages of doing an MDI?
2. Can I just add an MDI form to my initial SDI application, or do I have to start all over?
3. I can't seem to figue out how to edit my sub form in my existing application. The only Object and Code windows that shows up is the main form. How do I get the other forms to show in the Code and Object windows?

Any other recommendations are welcome.

[RhinoBull]

What are the advantages of doing an MDI?

There is only one as far as I'm concerned: to keep together multiple documents.

Can I just add an MDI form to my initial SDI application, or do I have to start all over?

Yes you can - after adding an MDI form you will have to set MdiChild property to True for each form you want to be an mid child.

I can't seem to figue out how to edit my sub form in my existing application. The only Object and Code windows that shows up is the main form. How do I get the other forms to show in the Code and Object windows?

Not sure I understand.

[si_the_geek]

You should stick to SDI - MDI is for programs like Word/Excel, where you can have multiple forms (Documents in Word/Excel) open at the same time, all of them being inside the parent form.

Anyhoo, for clarification here are answers to your questions:
1. It allows you to have several windows that the user can move between, in addition to the Word/Excel example, think about VB itself - it can have multiple code and/or object windows, as well as several extra single-instance windows (Properties, Immediate, ...).

2. You need to start over for the "parent" form. You can copy/paste a fair amount of it, but will not gain anything over an SDI application unless you make changes. (edit: RhinoBull covered the child forms)

3. Just select the form in the Project Explorer window (if you can't see it, use the View menu).

[RhinoBull]

You should stick to SDI...

I wouldn't be so categorical about it - as always it's matter of taste, business rules, requirements, necessity if you will, mdi limitations that you may (or may not) overcome, etc, etc, etc...