BUG: ALT+TAB Hangs MDI App with Activated OLE 2.0 Server

- Standard and Professional Editions of Microsoft Visual Basic for

  Windows, version 3.0

SYMPTOMS

The ALT+TAB keystroke combination may cause the computer to hang (stop responding to input) when an MDI application is an activated OLE 2.0 server in the MSOLE2.VBX control. It may also cause a general protection (GP) fault.

CAUSE

This problem is caused by MSOLE2.VBX when interpreting the menu negotiation protocol of some server applications.

WORKAROUND

The only way to work around this is to use the OLE control on a non-MDI form.

STATUS

Microsoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

MORE INFORMATION

Steps to Reproduce

1. Start a new project in Visual Basic. Form1 is created by default.

2. Add a new MDI form (MDIForm1).

3. Make Form1 an MDI Child by setting the MDIChild property to true.

4. Add an OLE2 control to Form1. Embed a new Word version 6.0 Document when the insert object dialog comes up.

5. Make MDIForm1 the start up form. From the Options menu, choose Project... and then Start Up Form. Select MDIForm1.

6. Add the following code to the MDIForm1 Load event:

   MDIForm1.Show Form1.Show Form1!Ole1.Action = 7

7. Save the project.

8. Make an EXE from the project.

9. Run the EXE with all other applications shut down.

10. Press ALT+TAB. The computer will lock up (hang).