>>
>>David,
>>
>>Yuppers! I've found that some ActiveX controls (like the ListView and TreeView) don't affect the ActiveForm property. Others, such as the MS Toolbar, do and end up as the ActiveForm.
>>
>>My hunch (and it's no more than that) is that it has to do with the nature of the control itself. Taking the Toolbar as an example, the most significant difference that I see is that the icons shown on the buttons can change depending on whether or not the button is disabled, enabled, "hot" (mouse over them), or "cold" (enabled but mouse not over them). The guess is here that this is goofing up the normal message processing that occurs otherwise.
>>
>>The only (and I must admit, rather tenuous) workaround I've implemented is to check the ActiveForm against the first form in the Forms collection.
>
>You might be close to the reason... I cannot remeber where I have seen it but AFAIR VFP has problems with ActiveXs that provide containership. Because VB Picturebox provides containership and we have derived this control in our ActiveX I suppose that this may be the reason for this strange bahaviour.
>
You may be thinking of MSKB#Q186123, which references the MS Coolbar. I must admit that the article came to mind to me as well. There is probably some relationship between the message handling of this and the MS Toolbar.