• Symptom 1
  When you try to debug Visual Basic for Applications (VBA) code in Visual Basic Editor, the Winword.exe process uses an average of 50 percent of the CPU resources in Windows Task Manager.
• Symptom 2
  When you try to run a modal UserForm in Visual Basic Editor, the Winword.exe process uses an average of 50 percent of the CPU resources in Windows Task Manager.
  
  Note By default, when you insert a UserForm into a VBA project, the UserForm is a modal UserForm.

Back to the top

1. In Visual Basic Editor, double-click ThisDocument in the Project Explorer window.
2. Add one of the following VBA code samples in the ThisDocument (Code) window.
   
   Sample 1

   Sub showform()
   <UserFormName>.Show vbModeless
   End Sub
   

   Sample 2

   Sub showform()
   <UserFormName>.Show 0
   End Sub
   

   Note UserFormName is the name of the UserForm that is displayed in the Project Explorer window.

Back to the top

Steps to reproduce problem 1

1. Create a new document in Word 2007.
2. On the Developer tab, click Visual Basic in the Code group to start Visual Basic Editor.
3. In the Project Explorer window, double-click ThisDocument, and then add the following code.

   Sub Hello()
   MsgBox "Hello"
   End Sub
   

4. On the Debug menu, click Step Into.
5. Start Windows Task Manager, and then click the Processes tab.
   
   Notice that the Winword.exe process uses an average of 50 percent of the CPU resources.

Back to the top

Steps to reproduce problem 2

1. Start Word 2007.
2. On the Developer tab, click Visual Basic in the Code group to start Visual Basic Editor.
3. On the Insert menu, click UserForm.
4. On the Run menu, click Run Sub/UserForm.
5. Start Windows Task Manager, and then click the Processes tab.
   
   Notice that the Winword.exe process uses an average of 50 percent of the CPU resources.

Back to the top