Elmer:

Thank you for your thoughtful reply on Modeless Forms. I have printed it out and will retain it as a reference.

But I am still trying to understand why programmers would choose a modeless format.

From your note there appear to be two issues.

1) The modeless form set permits shutdown without going back to the Quit button.

Well even if the operator is permitted to shutdown in the middle of something, he could lose all his work because the processes are only partially completed. My big toe feeling is that the operator is not going to see this as a benefit if the shutdown is too easy to do. There may be situations where he is building something all wrong and he realizes his error part way through and wants out without saving but I don't think this happens very often.

2) Modeless forms allow the operator to click from one form to another and back again.

I have never found a use for this feature. In my standard format, the operator does something in one screen and if he moves to an overlay screen (such as a pick list or edit box), the buttons on the underlying screen are disabled and he completes the pick list or edit box and goes back to the previous screen which is refreshed and re-enabled. This seems natural for my users. There may be some complex applications that require several screens open at one time but I simply have not come across that situation.

Nevertheless, Elmer, your memo has clarified the steps for me which I never understood before, so I will keep my mind open to opportunities to apply this feature.

Thanks again for your thoughtful reply.

Mike Smith