Article ID: 871045 - Last Review: May 18, 2007 - Revision: 1.3 BUG: An MDI child form may not maximize if the child form contains an ActiveX control in Visual Studio .NET 2003On This PageSYMPTOMSWhen you use an ActiveX control in a Multiple-Document
Interface (MDI) child form in Microsoft Visual Studio .NET 2003, you may
experience the following problems:
CAUSEThis problem occurs because your application may not treat forms as
correct MDI child forms when the following conditions are true:
WORKAROUNDTo work around this
problem, use one of the following methods: Method 1Modify the code so that you can maximize the child form, and then modify the code so that you can obtain the focus of an inactive child form:
Method 2Set the MdiParent property and the WindowState property of the child form before you call the InitializeComponent method in the child form. To do this, you must write code that creates a constructor that takes the MdiParent property and the WindowState property as arguments and that creates a form as an MDI child form:
STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. MORE INFORMATIONSteps to reproduce the behavior
REFERENCESFor more information, visit the following Microsoft
Developer Network (MSDN) Web sites: Creating MDI parent
forms http://msdn2.microsoft.com/en-us/library/aa984330(VS.71).aspx (http://msdn2.microsoft.com/en-us/library/aa984330(VS.71).aspx) Creating MDI child forms http://msdn2.microsoft.com/en-us/library/aa984329(VS.71).aspx (http://msdn2.microsoft.com/en-us/library/aa984329(VS.71).aspx) | Article Translations
|
Back to the top
