Visual Basic

Sub CommentImporter()

Dim myFile As String
Set myCell = ActiveCell
Dim myCellvalue As String
Dim Item As Integer
Dim myRow As Integer
Dim myCol As Integer
myRow = 0
Item = 0

myFile = InputBox("Give the path of the file desired to be scanned")
Set WordApp = CreateObject("Word.Application")
Set WordDoc = WordApp.Documents.Open _
    (myFile)
    WordApp.Visible = False
For Each Comment In WordDoc.Comments
    myCol = 0
    With Comment
        If Left(.Reference.Paragraphs(1).Style, Len("Heading ")) = "Heading " Then
        Else
            .Reference.GoToPrevious (wdActiveEndAdjustedPageNumber)
        End If
        Item = Item + 1
        myCell.Offset(myRow, myCol).Value = Item
        myCol = myCol + 1
        
        'Page = .Reference.Information(wdActiveEndAdjustedPageNumber)
        myCell.Offset(myRow, myCol) = Page
        myCol = myCol + 1
        
        'Section = .Reference.GoToPrevious(wdGoToHeading).Paragraphs(1).Range.ListFormat.ListString
        myCell.Offset(myRow, myCol) = Section
        myCol = myCol + 1
        
        'Line = .Reference.Information(wdFirstCharacterLineNumber)
        myCell.Offset(myRow, myCol) = Line
        myCol = myCol + 1
        
        Author = .Author
        myCell.Offset(myRow, myCol) = Author
        myCol = myCol + 1
        
        Doctext = .Scope.Text
        Doctext = Replace$(Doctext, Chr(13), Chr(10))
        
        Text = .Range.Text
        myCell.Offset(myRow, myCol) = Doctext + " : " + Text
        myCol = myCol + 1
        
        myRow = myRow + 1

        End With
        Next


WordApp.Quit SaveChanges:=wdDoNOtSaveCanges
Set WordApp = Nothing
End Sub

Sigh... It seems that many readers missed my original point. The ideas was not to encourage VB programmers to use CreateThread with Visual Basic. It was to explain clearly and accurately why you shouldn't use CreateThread with Visual Basic.

So, when Visual Basic 6 turned out to be considerably less thread-safe than VB5, breaking the sample programs referenced by this article, what could I do? I suppose I could go back and revise the samples and try to make them work with VB6. But then the same problem might arise with later versions of Visual Basic as well. 

Visual Basic offers good support of multithreading including multithreaded clients in ActiveX servers (this is described quite thoroughly in the latest edition of my Developing COM/ActiveX components book). I strongly encourage you to stay within the rules defined by the Visual Basic documentation and not use the CreateThread API with Visual Basic.

For those who insist on pursuing CreateThread further, to start with you should eliminate all Declare statements and use a type library instead. I don't promise that this will fix the problem, but my initial testing indicates that it is a necessary first step.