Arnon,
I had hoped to avoid such a re-design issue, but I presume you thought long and hard before switching.
I would like to know if this is simply just another bug, or is there an ActiveX design issue here that won't go away?

Thanks,
Conor



>Conor,
>We had all sort of problem with ActiveX and modal form, in the end we
>implemented form modality (ie a form is not really modal- but it is deemed
>so by its parent - other forms can still be opened) which also was good for
>other things we needed
>
>Arnon
>
>
>>
>>I've encountered a problem with the TreeView control relating to modal
>forms. If I invoke a modal form, from a form that has an activex control,
>and then a modeless form with a treeview, the NodeClick event (with custom
>code) does not fire.
>>Looking through the MSDN CD's I see numerous references to problems
>relating to using modal forms. I am guessing this is to do with the idea of
>the AUTOYIELD property. I see that a modal form in Windows is VERY different
>to a modeless form in terms of message handling. One suggestion which does
>not directly relate to this problem, involved using a timer and a DoEvents
>call to try and force a parent form to behave (the example related to a
>ListView not behaving). I'm trying to see if the concept may apply, but if
>anyone has any ideas (or a technical explanation) please reply.
>>Also when using a ListView I can't get the HITTEST method to work
>correctly. I got a solution for the TreeView using API calls to GETMETRICS
>but the factors don't seem to relate to the ListView. Any ideas?