Hi Peter,

Wouldn't it drive users nuts if accidental click outside of a form would close it?

>Hi All,
>
>In the old foxpro (fpw,fpd) you can create a modal screen, then invoke another screen, and then successfully click on the modal screen which will be reactivated. Clicking on the second screen will then only succeed if it was declared in the modal screen's READ MODAL WITH clause.
>
>In vfp I invoke a modal form FORM_M, then I invoke another form FORM_2, e.g. with ON KEY LABEL F7 DO FORM FORM_2. The second form_2 pops up and gets focus. In the deactivate method I have code to get rid of the second form_2. Clicking outside the form_2 on a nonmodal form will indeed close the second form_2. However, clicking on the modal form_m has NO EFFECT. Well, that's to say, it will invoke a beep.
>
>I don't understand the logic. Who can explain this behavior, which of course is by design.
>
>Oh yes, before I forget: As second form I've tried a MODAL form and a NONMODAL form. However, same behavior occurs no matter what its type is. Both will invoke a beep.
>
>Any suggestions on how to get rid of the second form by clicking outside the form?