{"id":52193,"date":"2009-10-22T00:01:00","date_gmt":"2009-10-22T00:01:00","guid":{"rendered":"https:\/\/blogs.technet.microsoft.com\/heyscriptingguy\/2009\/10\/22\/hey-scripting-guy-part-2-how-can-i-update-many-office-word-documents-at-once\/"},"modified":"2009-10-22T00:01:00","modified_gmt":"2009-10-22T00:01:00","slug":"hey-scripting-guy-part-2-how-can-i-update-many-office-word-documents-at-once","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/scripting\/hey-scripting-guy-part-2-how-can-i-update-many-office-word-documents-at-once\/","title":{"rendered":"Hey, Scripting Guy! Part 2: How Can I Update Many Office Word Documents at Once?"},"content":{"rendered":"

\"Bookmark<\/a> <\/p>\n

(Editor’s note<\/strong>: This is part 2 of a two-part article originally intended for TechNet Magazine<\/em>. Part 1 was published yesterday<\/a>.) <\/p>\n


Now we arrive at the entry point to the script. The first thing to do in the entry point of the script is to create a collection of all the .doc and docx files in the folder indicated by the $path<\/b> variable. The Get-ChildItem<\/b> cmdlet is used to gather the collection of files. The Recurse<\/b> parameter is used to tell the Get-ChildItem<\/b> cmdlet to retrieve all files in the path that match the Include<\/b> filter. This is seen here: <\/p>\n

$files = Get-ChildItem -Path $path -Include *.doc,*.docx –Recurse<\/p>\n

<\/font><\/span><\/p>\n

The ReplaceWordsLogResults.ps1 script can be used to make nomenclature changes in a collection of documents. It can also be used to automatically correct misspelled words and to improve the grammar of documents. Such a candidate for improvement is seen here:<\/p>\n

<\/a><\/p>\n


There is no way to completely automate the grammar checker and the spelling checker from within Microsoft Word. There is a find-and-replace method that can be used to perform the same service. To allow the script to work with multiple words, a hash table is created. Each element of the hash table is made up of a key and a value. Each element in the hash table is separated from other elements by a semicolon. The hashtable is stored in the variable $wordHash<\/b> and is seen here: <\/p>\n

$wordHash = @{“misspelled” = “spelled incorrectly” ; “done”=”finished”}<\/p>\n

<\/font><\/span><\/p>\n

The log file name is stored in the $logfile<\/b> variable. The log will be a comma-separated value file so that it can easily be opened in Microsoft Excel. A counter variable, $i<\/b>, will be used to keep track of the progress as the script walks through the collection of files. This is seen here: <\/p>\n

$logfile = “ReplaceResults.csv”<\/p>\n

<\/font><\/span><\/p>\n

$i=0<\/p>\n

<\/font><\/span><\/p>\n

The Find object<\/font><\/a> is used to perform the find-and-replace operation in the Word document. The find operation represented by the find<\/b> object begins when it is called by the Find.Execute method<\/font><\/a> of the find<\/b> object. The execute<\/b> method takes a large number of parameters. The easiest way to deal with complicated methods such as the execute<\/b> method is to create a collection of variables that contain the desired parameters. This makes the method call easier to read and also makes the script easier to modify. The variables that hold the preferences for the execute<\/b> method are seen here: <\/p>\n

$ReplaceAll = 2<\/p>\n

<\/font><\/span><\/p>\n

$FindContinue = 1<\/p>\n

<\/font><\/span><\/p>\n

$MatchCase = $False<\/p>\n

<\/font><\/span><\/p>\n

$MatchWholeWord = $True<\/p>\n

<\/font><\/span><\/p>\n

$MatchWildcards = $False<\/p>\n

<\/font><\/span><\/p>\n

$MatchSoundsLike = $False<\/p>\n

<\/font><\/span><\/p>\n

$MatchAllWordForms = $False<\/p>\n

<\/font><\/span><\/p>\n

$Forward = $True<\/p>\n

<\/font><\/span><\/p>\n

$Wrap = $FindContinue<\/p>\n

<\/font><\/span><\/p>\n

$Format = $False<\/p>\n

<\/font><\/span><\/p>\n

The collection of Word documents that were obtained by the Get-ChildItem<\/b> cmdlet is piped to the ForEach-Object<\/b> cmdlet. This is seen here: <\/p>\n

$files | ForEach-Object {<\/p>\n

<\/font><\/span><\/p>\n

The $file<\/b> variable is used to store the complete path to each Word document that comes across the pipeline. This is seen here: <\/p>\n

  <\/span>$file = $_.fullname<\/p>\n

<\/font><\/span><\/p>\n

The $i<\/b> counter variable is incremented by one as seen here: <\/p>\n

  <\/span>$i ++<\/p>\n

<\/font><\/span><\/p>\n

Next the Write-Progress<\/b> cmdlet is used to display a progress bar. The progress bar shown in the following image is the one displayed by the Windows PowerShell ISE on Windows PowerShell 2.0. The progress bar gives a visual indicator that the script is running and is continuing to process Word documents. This is the only visual indicator that the script is running or has completed:<\/p>\n

\"Image<\/p>\n

The code that calls the Write-Progress<\/b> cmdlet is seen here: <\/p>\n

  <\/span>write-progress -activity “Searching For Word documents” <\/p>\n

<\/font><\/span><\/p>\n

 <\/span>-status “Progress:” -percentcomplete ($i\/$files.count*100)<\/p>\n

<\/font><\/span><\/p>\n

The Get-WordSelection<\/b> function is used to create the Word application<\/b> object and to create the selection<\/b> object. The Get-WordSelection<\/b> function accepts two parameters, the path to the Word document, and whether or not to make the Word application visible while processing the files. This is seen here: <\/p>\n

 <\/span>Get-WordSelection -file $_.fullname -visible $false<\/p>\n

<\/font><\/span><\/p>\n

Now it is time to walk through the hash table that contains the words and their substitute values. The keys<\/b> property is used to obtain a collection of all the keys in the hash table. This is seen here: <\/p>\n

 <\/span>foreach($FindText in $wordHash.keys)<\/p>\n

<\/font><\/span><\/p>\n

 <\/span>{<\/p>\n

<\/font><\/span><\/p>\n

Armed with a specific set of keys and values, it is time to search the Word document for specific words. The words that are sought are stored in the keys of the hash table. The substitute word is the value associated with the key<\/b> value. To retrieve the value associated with a particular key, the value is retrieved by querying the specific key. Each key in the collection of keys from the hash table is queried. This is seen here: <\/p>\n

  <\/span>$rtn = $Script:Selection.Find.Execute($FindText,$MatchCase,<\/p>\n

<\/font><\/span><\/p>\n

   <\/span>$MatchWholeWord,$MatchWildcards,$MatchSoundsLike,<\/p>\n

<\/font><\/span><\/p>\n

   <\/span>$MatchAllWordForms,$Forward,$Wrap,$Format,<\/p>\n

<\/font><\/span><\/p>\n

   <\/span>$wordHash.$FindText,$ReplaceAll) <\/p>\n

<\/font><\/span><\/p>\n

 <\/span>} #end foreach findtext<\/p>\n

<\/font><\/span><\/p>\n

The modified Word document is seen here:<\/p>\n

\"Image<\/p>\n

 <\/p>\n

After the Execute<\/b> method from the Find<\/b> object has been called and all the replacements that are stored in the hash table have been made, it is time to call the New-LogObject<\/b> function. This function accepts two parameters: the path to the Word document and the Boolean return value that was captured from the Execute<\/b> method. This is seen here: <\/p>\n

 <\/span>New-LogObject -document $file -replaced $rtn<\/p>\n

<\/font><\/span><\/p>\n

One reason to pipe the collection of Word documents to the ForEach-Object<\/b> cmdlet is that it makes it easy to create a CSV file from the logging object that is returned from the New-LogObject<\/b> function. A new logging object is created for each Word document that is processed. The Export-Csv<\/b> cmdlet includes the properties on the first line of the CSV file and the values on the second line. There is no append<\/b> parameter for the Export-Csv <\/b>cmdlet. The Export-Csv<\/b> cmdlet is designed to handle piped data, and each logging object is therefore piped to the Export-Csv<\/b> cmdlet without incurring extra property descriptions. This command is seen here: <\/p>\n

} | Export-Csv -Path (join-path -Path $path -ChildPath $logfile) -NoTypeInformation<\/p>\n

<\/font><\/span><\/p>\n

$Script:word.quit()<\/p>\n

<\/font><\/span><\/p>\n

The completed log is seen here:<\/p>\n

\"Image<\/p>\n


Though I do not think this script will stand the test of time, it should make it easier for you to cope with many of the changes that take place on a daily basis in the workplace. Whether you use the ReplaceWordsLogResults.ps1 script to fix common typographical errors or standard letter transpositions, or to update documents with the latest and greatest naming conventions, you are sure to find a use for it. <\/p>\n

For more tools, tips, and tricks to help you surf the tides of change, head over to the TechNet Script Center<\/a> and check out our daily Hey, Scripting Guy! Blog posts. <\/p>\n

Ed Wilson and Craig Liebendorfer, Scripting Guys<\/span><\/b><\/p>\n

<\/p>\n

<\/span><\/b> <\/p>\n","protected":false},"excerpt":{"rendered":"

(Editor’s note: This is part 2 of a two-part article originally intended for TechNet Magazine. Part 1 was published yesterday.)  Now we arrive at the entry point to the script. The first thing to do in the entry point of the script is to create a collection of all the .doc and docx files in […]<\/p>\n","protected":false},"author":595,"featured_media":87096,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1],"tags":[84,49,3,45],"class_list":["post-52193","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-scripting","tag-microsoft-word","tag-office","tag-scripting-guy","tag-windows-powershell"],"acf":[],"blog_post_summary":"

(Editor’s note: This is part 2 of a two-part article originally intended for TechNet Magazine. Part 1 was published yesterday.)  Now we arrive at the entry point to the script. The first thing to do in the entry point of the script is to create a collection of all the .doc and docx files in […]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/posts\/52193","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/users\/595"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/comments?post=52193"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/posts\/52193\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/media\/87096"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/media?parent=52193"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/categories?post=52193"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/tags?post=52193"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}