Article ID: 326251 - View products that this article applies to.
This article was previously published under Q326251
This article has been archived. It is offered "as is" and will no longer be updated.
If you have a composite Windows Forms control that is hosted as an ActiveX control, and focus is on one of the child controls where the TabIndex is not: TabIndex = 0, the control does not reactivate if you deactivate the control, and then try to reactivate the control.
A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next .NET Framework service pack that contains this hotfix.
To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:
http://support.microsoft.com/contactus/?ws=supportNOTE: In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The typical support costs will apply to additional support questions and issues that do not qualify for the specific update in question.
The English version of this fix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
Date Time Version Size File name --------------------------------------------------- 07-Aug-2002 20:20 1.0.3705.301 1,982,464 System.windows.forms.dll
Microsoft has confirmed that this is a problem in the .NET Framework, versions 1.0, SP1.
Using Windows Forms controls in any ActiveX containers other than Microsoft Internet Explorer is not supported.