.Net user control in a VB6 app requires double-click to activate

26 Sep 2006 5:08 PM

holysmokes99

I have a VB6 winforms application that has a .Net 2.0 user control
(exposed via COM) that I made. No matter what I have tried, once the
user control looses focus, it always requires a double-click to regain
focus. My control is in a Microsoft VB6 Tab control. So whenever I go
to another tab, and return to the tab with the user control, I must
double-click the control to give it focus. I have tried giving it focus
in code, passing a double-click event to the control, tried using the
3rd-party SStab control for the tab functionality, but it all has no
effect.

A friend was just telling me something about Microsoft changing the way
Active-X controls were activated in websites now due to some lawsuit,
something about needing to double-click on them. Could this have
ANYTHING to do with it? As I said, I am using the 2.0 framework.

Thanks for any suggetsions,
Marcus

28 Sep 2006 4:21 PM

Mike Lowery

<holysmoke***@hotmail.com> wrote in message
Show quoteHide quote

news:1159290533.403518.105600@h48g2000cwc.googlegroups.com...
>I have a VB6 winforms application that has a .Net 2.0 user control
> (exposed via COM) that I made. No matter what I have tried, once the
> user control looses focus, it always requires a double-click to regain
> focus. My control is in a Microsoft VB6 Tab control. So whenever I go
> to another tab, and return to the tab with the user control, I must
> double-click the control to give it focus. I have tried giving it focus
> in code, passing a double-click event to the control, tried using the
> 3rd-party SStab control for the tab functionality, but it all has no
> effect.
>
> A friend was just telling me something about Microsoft changing the way
> Active-X controls were activated in websites now due to some lawsuit,
> something about needing to double-click on them. Could this have
> ANYTHING to do with it? As I said, I am using the 2.0 framework.

If you're using an ActiveX control in a browser window, this is likely the
problem. Your friend is correct; Microsoft made a change in the way ActiveX
controls are handled within IE:
http://support.microsoft.com/kb/912945