BUG: Automation client receives an error message or crashes when the client calls the Find object in Word

Steps to reproduce the problem

1. Find the Excel 5.0 type library (Xl5en32.olb), and then register it by typing Regtlib at a command prompt.
2. In Visual Basic, create a Standard EXE project. Form1 is created by default.
3. Add a button to Form1, and then paste the following code example in the code section for Form1.

   Private Sub Command1_Click()
      Dim oApp As Word.Application
      Dim oDoc As Word.Document
      Dim oSel As Word.Selection
         
      Set oApp = New Word.Application
      oApp.Visible = True
      
      Set oDoc = oApp.Documents.Add
      Set oSel = oApp.Selection
      
      oSel.TypeText "This is a test. You too can automate Word."
      oSel.Start = 0
      
      oSel.Find.Execute "Word", , , , , , True, _
         wdFindContinue, , "Microsoft Word 2000", wdReplaceAll
         
      MsgBox "Did it work?"
      
      Set oSel = Nothing
      oDoc.Saved = True
      oDoc.Close
      Set oDoc = Nothing
      
      oApp.Quit
      Set oApp = Nothing
      
   End Sub
   

4. On the Project menu, click References.
5. In the References dialog box, select Microsoft Word 8.0 Object Library (or select the Word 9.0 Object Library, the Word 10.0 Object Library, or the Word 11.0 Object Library), and then click OK.
6. Compile and run the code, or press F5 to run the code in the debugger. Click the command button. You receive the error message that is described in the "Symptoms" section.
7. Fix the issue by reregistering the Word type library as described in the "Resolution" section. Or, replace the early-bound declaration of the Selection object to use late binding with the following code example.

       Dim oSel As Object