MDI forms

[FinChase]

There seems to be a difference of opinion on this forum as to using MDI forms. Here's my situation: I have an app that uses an Access DB as a backend. When user's open the app a dialog box opens so they can choose the correct database for their project. There is one child form which contains an SS tab control. My users have requested that I limit the number of tabs, as they found multiple pages of information in previous releases of the app to be confusing. Therefore, I am trying to fit all the info into just three tabs, so I was taking advantage of the fact that most of the time, my users will be working on 17-inch monitors. However, occasionally users may have to work on laptops and will lose a lot of the controls on the app.

It appears that if I use an MDI form I must redesign the app layout smaller with more tabs (and displeasing users). Is there a different approach I should take instead of an MDI form?

[Joacim Andersson]

I'm a little confused about your question. When you say that you have a child form that contains several tabs, do you mean a MDI Child form?

Personally I don't have anything against MDI application, they fill there purposes for some applications but can be confusing for others.

There are of course alternatives to both the use of tabbed interface dialogs and MDI apps. Instead of tabs you could use a treeview on the left hand side of the window or use an Outlook like bar. Have a look at this screen shot for an example:
http://www.sourceedit.com/sshots.asp?image=9

Best regards