Go Premium for a chance to win a PS4. Enter to Win

  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 228
  • Last Modified:

MS word bat script to determine if a file has track changes on and if there are changes

Hi Experts, I have about 50,000 word documents sitting on a file server as part of an application that I support.  There was an issue where some of the files - no telling how many - we're saved with track changes on and unaccecpted changes to the document (I.e., the red text).  I need to write a program that will examine each file and determine if A) track changes is enabled, B) if there are any unaccecpted changes, C) when the file was last modified, D) who modified it.

I'm thinking that this information is stored in the metadata of the file somewhere, or at least in the file properties.  I believe a batch program would be the easiest way to do this with the output going to a .txt or .csv file.  I would actually be more comfortable if there were a VBA program that I could run out of Excel that could do the analysis ( I'm pretty good with VBA)

Any suggestions would be much appreciated - I'm in kind of a crunch here.

- Jamey
  • 2
1 Solution
JamesCburyAuthor Commented:
for anyone tracking this thread I think I might have figured something out... please comment if there are issues here.   to get to the track changes data I had to open the file, pull the attributes, close the file.  It does what I want it to, but is a bit clunky...
Sub Check_track_changes()

    'Clear the existing data
    Range([C7], Cells([C7].End(xlDown).Row, 11)).ClearContents
    'set the directiory folder
    sFolder = ActiveSheet.Range("FD_Path")
    'set the doc types in scope
    sExt = Array(".doc", ".docx", ".docm")
    Set oFSO = CreateObject("Scripting.FileSystemObject")
    Set oFolder = oFSO.GetFolder(sFolder)
    Set oShell = CreateObject("Shell.Application")
    Set oNamespace = oShell.Namespace(sFolder)
    Set wApp = CreateObject("Word.Application")
    iRow = 7
    For Each oFile In oFolder.Files
        For E = 0 To UBound(sExt)
            If LCase(Right(oFile.Name, Len(sExt(E)))) = sExt(E) Then
                'log the open time *Debugging purposes*
                Cells(iRow, 9) = Now()
                'Update the progress
                [D3] = "Now Processing File " & iRow - 6 & " of " & oFolder.Files.Count
                'write the file name(from metadata)
                Cells(iRow, 3) = oFile.Name
                'Open the file to get attributes
                'wApp.Visible = True
                On Error GoTo Bad_File_Err
                Set myDoc = wApp.Documents.Open(Filename:=oFile.Path, ReadOnly:=True)
                On Error GoTo 0
                'Check if track changes is on
                If myDoc.TrackRevisions = True Then
                    Cells(iRow, 4) = "On"
                ElseIf myDoc.TrackRevisions = False Then
                    Cells(iRow, 4) = "Off"
                End If
                'Get the count of changes
                Cells(iRow, 5) = myDoc.Revisions.Count
                'Get the count of comments
                Cells(iRow, 6) = myDoc.Comments.Count
                'Close the file **DO NOT SAVE CHANGES**
                myDoc.Close SaveChanges = False
                'Application.ActiveDocument.Close SaveChanges:=wdDoNotSaveChanges
                'Get the date modified (from metadata)
                Cells(iRow, 7) = FormatDateTime(oFile.DateLastModified, 2)
                'log the close time *Debugging purposes*
                Cells(iRow, 10) = Now()
                Cells(iRow, 11) = Cells(iRow, 10) - Cells(iRow, 9) 'calculate the cycle time
                iRow = iRow + 1
            End If
        Next E
    Next oFile
    [D3] = ""
Exit Sub

    Cells(iRow, 4) = "Cannot open this file - check for corruption"
    Cells(iRow, 9) = "Failed"
    GoTo Resume_Files
End Sub

Open in new window

Phillip BurtonCommented:
Track Changes is not part of the metadata - see http://www.filecats.co.uk/metadata-extended-document-properties/microsoft-office/ for details of Word's metadata. You can certainly get Author and last saved as part of the metadata, and if you are in a time crunch, Filecats Professional might be a good idea.

The only way to ascertain if Track Changes is on is to open each of the files like James is doing. Do bear in mind that, if you do that, it MAY change some of the time metadata such as Last Accessed (emphasis on MAY), even if not saved. So I would suggest cataloguing in Filecats Professional first (which doesn't affect such data), and then doing James' solution, and combining the two.
JamesCburyAuthor Commented:
Thanks Phillip - that's good advice.  I will make that update to my program for future use.
It may not be part of the official metadata, but Track Changes IS a saved flag. I'm not certain how this would be read in an older .doc Word file, but it's pretty easy in .docx. All of the newer Office formats that end in "x" are actually ZIP files that contain a variety of resources, so it's very easy to discover in the XML.

Basically, you'd write a script that unzipped the file (some 3rd party libraries might let you just decompress a single file into memory, which would be even faster). In the resulting "word" subfolder, you'll have 2 files that have the info you want - document.xml and settings.xml.

If Track Changes is enabled, then the settings.xml file will contain this text:

If there are revisions, then the document.xml file will contain a tag that starts with <w: and indicates the operation, like "<w:del", and it will have a "w:date" attribute, and a "w:author" attribute, like this:

<w:del w:id="1" w:author="Fooey Barress" w:date="2016-02-10T20:42:00Z">

You can use Xpath syntax to search for such tags using most major XML libraries.

The older pre-2010 formats use a proprietary binary format that would require a separate library to read, assuming the Office SDK doesn't give you the necessary info.

In any event, reading the data like this should give you a good idea without risking any modifications to the file AND it has the added bonus of not requiring an instance of Word running in memory to open/close all that stuff.

Featured Post

Configuration Guide and Best Practices

Read the guide to learn how to orchestrate Data ONTAP, create application-consistent backups and enable fast recovery from NetApp storage snapshots. Version 9.5 also contains performance and scalability enhancements to meet the needs of the largest enterprise environments.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now