The information in this article applies to:
SYMPTOMSThe following code worked in Visual Basic 4.0, but fails in Visual Basic 5.0 or 6.0 with an error "Error 380, Invalid Property Value" if an MDI parent form is in the project:
CAUSEMDI forms do not have a MDIChild property in Visual Basic 4.0, 5.0, or 6.0. Visual Basic 4.0 compensated for that in the specific case of looping through the forms collection and checking this property, but Visual Basic 5.0 and 6.0 do not. RESOLUTIONThe workaround is to determine if the form is an MDI form before checking the MDIChild property, which the following code demonstrates:
STATUSMicrosoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article. We are researching this bug and will post new information here in the Microsoft Knowledge Base as it becomes available. Additional query words:
Keywords : kberrmsg kbnokeyword kbVBp500bug kbVBp600bug kbGrpVB |
Last Reviewed: January 5, 2000 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |