I agree.
MDI, like the name suggests, is used to open multi documents in the
same app, or to open the same document using different tools. The VB
IDE is an example. You open a 'project' made of different 'modules'
and for each module you have different tools, like the code editor,
the form editor, the property dialog and so on.
There are no resource problems on using an MDI. I prefer to use it
when the application has too many modeless forms open at the same time.
I do not like having floating dialogs open all over the desktop.

Marco 

-----Original Message-----
From: Walt Morgan [mailto:wmorgan@s...]
Sent: Friday, July 26, 2002 12:46 PM
To: professional vb
Subject: [pro_vb] MDI


TJ,

I've an application that I chose a MDI interface. My reasons for doing so do
not fit neatly into the MDI model. One of the things said about MDI is a
consistent menu interface for the user. Frankly, I use it in order to
minimize my entire application and be able to restore it from the startbar.
Also, I allow the user to have multiple tables open and in view in order for
them to see certain relationships without having to switch around.

I'm sure it's all a matter of choice. Since creating that application I've
seen where I could have improved upon the interface, but I do not regret
using the MDI.

Hope this helps a little,

Walt