If the controls simply popup more form nests for the end user to deal with - then perhaps your right. There can be too many controls. A well integrated use of navigators, tool bars and buttons and menus can be helpful as long as the available service doesn't conflict with the active service. Lots of times there are shared control functions. A tool bar button - a menu and a cmd button will push the same service to the desktop. I guess this redundancy is good - some users have experience with menus - others just buttons. A well structured and written application will always be simple to use. The user has enough decisions to make. Why force them to deal with a non-intuitive interface.

Too many nested froms can be confusing. Tool tips can be helpful. Just sampling a well designed commercial interface - like Quick Books - would be helpful for many developers. Imitate the big boys!

Are you using a commercial framework?


>Hi,
>
>I believe that simple screens (both client/server and HTML) with fewer controls get fewer telephone calls for support from clients.
>
>I'm looking for some studies or information that discuss this issue. I'd like to reference these studies in a note on screen and menu design that I'm writing for a client.
>
>Thanks in advance.
>
>
>Paul de Niverville