the keywords in the document properties word 10

$docs = Get-childitem -path $Path -Recurse -Include $include $application = New-Object -ComObject word.application $include = “Title”,”Author”,”Keywords”, “Number of words”, “Number of pages” This portion of the script is shown here. Finally, I obtain a collection of fileinfo objects and store the returned objects in the $docs variable. The reason for creating WdSaveOptions is to keep Word from modifying the last save option on the Word files. Next, I need to create BindingFlags and WdSaveOptions. Next, I create the Word.Application object and set it to be invisible. This permits changing the path to search, as well as modifying the include filter that is used by the Get-ChildItem cmdlet.

The first thing I do is create a couple of command-line parameters. You should refer to those blogs for additional information. It is very difficult to work with Word document properties, and I have written several blogs about this. This is a great benefit because it permits further analysis and processing of the data-and it would even permit export to a CSV file if I wish. This script also accomplishes a few of the things I wanted to do in yesterday’s script that I did not get a chance to do-namely, I return a custom object that contains the built-in properties I choose. Today’s script is similar to the Find All Word Documents that Contain a Specific Phrase script from yesterday, so reviewing that posting would be a good thing to do.

Creates a custom Windows PowerShell object with each of the specified properties, in addition to the full path to the Word document.

Retrieves the specific built-in Word properties and their associated value.

The built-in Word properties are listed on MSDN.

Creates an array of specific Word document properties from the Word built-in document properties enumeration.

Searches a specific folder for Word documents.

Well the script for today took a bit of work … actually it took quite a bit of work. Microsoft Scripting Guy, Ed Wilson, is here.

Summary: Microsoft Scripting Guy, Ed Wilson, talks about using Windows PowerShell to find specific built-in properties from Word documents.

The keywords in the document properties word 10