Claudio,

> Why do you still need to use modal form if you need to produce Drag and Drop operations.
>
> Probably the better option to you is set the yourform.ALWAYSONTOP propertie to .T., if you want to left your form on the top of the others. The behavior is almost the same. If ocassionaly the user start one new event from other form, you can control the operation with one "status flag" variable allowing or not the event run.

The reason why I want the form to be modal is due to the process flow of the application. Also, I am not dragging/dropping from one form to another. I am using a single form to either drag/drop from within a treeview or from one treeview to another. Making the form modal apparently prevents the OLEDragMove event from even firing.

I'm using the SYS(2033,0) call to disable dual ActiveX, per MSDN articles. Also, I'm using the _VFP.AutoYield = .F. in the form's INIT(). I hope that I am missing something here and that it is possible within the VFP language to have a modal form that does not inhibit ActiveX controls events from firing. Otherwise, I hope that SP5 or VFP7 addresses this lame behavior.

Doug