PRB: ActiveX Control Click Event Not Firing When Form Is Modal

MORE INFORMATION

When adding code to the Click event of an ActiveX or Threed control, normally the code in the Click event fires when that control is clicked regardless if the form is a modeless or modal form. If that form is modal and called from a ActiveX or Threed control on another form, then the code in the Click event of that ActiveX or Threed control does not fire. For the code to fire correctly, the form that is called has to be modeless or the control that calls the form with the ActiveX or Threed control has to be a standard FoxPro control.

Steps to Reproduce Behavior

When using Visual FoxPro 3.0, substitute the phrase "Threed control" for "ActiveX control" in the following steps:

1. Create two forms called Active1 and Active2, respectively, and add an ActiveX control (the Threed Command button will do) to each form.
2. In the Active2 form change the WindowType property to Modal and add the following code to the Click event of the ActiveX control:

         WAIT WINDOW "ActiveX Control"
   						

3. In the Active1 form add a FoxPro command button and add the following code to the Click event of the ActiveX control and the Click event of the Visual FoxPro command button:

         DO FORM Active2
   						

4. Run the Active1 form and click on the ActiveX control. When the Active2 form appears, note that clicking on its ActiveX control does not fire the WAIT WINDOW command.
5. Close the Active2 form and click on the standard command button on the Active1 form. Note that the WAIT WINDOW command fires when clicking the ActiveX control on the second form.
6. Close the Active2 form, modify the form, and change the WindowType property in the Active2 form to modeless. Note that when the Active2 form is called from the ActiveX control on the Active1 form, the code fires properly when clicking on the ActiveX control on the Active2 form.