>You'll have to forgive me if this question seems a little silly but it's about time that I ask. In the programming I've done the only time that I saw a reason for a modeless form was when I wanted to alert the user to something but wanted processing to continue in the background. I could have done this with a wait window but they're so ugly.
>
>But other than that, I've never had need of a modeless form. Yet, it's the default. So I'm figuring there must be something I'm missing. Could someone please clue me in on the usefulness of modeless forms? Thanks.

Modal forms are single interface forms - normally used for displaying or requesting information where the user must exit the form before anything else can happen. When you call a modal form, control is held by the modal form. Modeless forms - you can have many forms open at the same time (some hidden) and the user can freely go between forms. They require a lot more control by the developer but open the doors to whatever you want the app to do! Also the first form is loaded and initialised but control is not passed to it until you issue a READ EVENTS so you can open the form and do some work with it BEFORE the user gets hold of it.