The information in this article applies to:
SYMPTOMS
While debugging your application in Break mode, Visual Basic may terminate,
hang, or cause one or both of the following errors when you end the
application:
-or-
NOTE: The memory address at which the error occurs may vary. CAUSEThis problem can occur when multiple forms are shown modally. The problem only occurs at design-time when you use the Immediate Window while in Break mode and then end the application. RESOLUTIONOne workaround for this problem is to avoid using the Immediate Window while your forms are shown modal or to show your forms modeless instead of modal. You can show a form modeless yet simulate most of the functionality of showing a form modal by setting the form's ShowInTaskbar property to False and by setting the Enabled property of the other visible forms to False, which prevents users from setting focus to the other forms. When the user dismisses the form, reset the Enabled property of the other visible forms as appropriate. STATUS
Microsoft 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.
MORE INFORMATIONSteps to Reproduce Behavior
Additional query words:
access violation illegal operation page fault ipf Gpf kbVBp500bug
Keywords : kbGrpVB |
Last Reviewed: January 5, 2000 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |