After spending some time on this over the past few days, and sorting through the spotty documentation provided by Microsoft on Accessibility, I was able to get a handle on the COM object in Microsoft Word 2007.  It turns out to be pretty simple, and is actually in the documentation they provide here, but they don’t make it clear as day.  I intend to do that here.

First we obtain the hwnd of the Microsoft Word Process:

//The main window in Microsoft Word has a class name of OpusApp
HWND wordWindow = FindWindow(L"OpusApp", NULL);

We can then traverse the child windows until we find the one with classname _WwG:

//Use the EnumChildWindows function to iterate through all child windows until we find _WwG
EnumChildWindows(wordWindow, (WNDENUMPROC) EnumChildProc, (LPARAM)1);

static BOOL EnumChildProc(HWND hwnd, LPARAM)
{
     WCHAR szClassName[64];
     if(GetClassNameW(hwnd, szClassName, 64))
     {
          if(_wcsicmp(szClassName, L"_WwG") == 0)
          {
               //Get AccessibleObject
               Word::Window* pWindow = NULL;
               HRESULT hr = AccessibleObjectFromWindow(hwnd, OBJID_NATIVEOM, __uuidof(Word::Window), (void**)&pWindow);
               if(hr == S_OK)
               {
                    //Word object is now in pWindow pointer, from this you can obtain the document or application
                    Word::_Document* pDoc = NULL;
                    pWindow->get_Document(&pDoc);
               }
               return false;     // Stops enumerating through children
          }
     }
	 return true;
}

Next we obtain our Word::Window object through AccessibleObjectFromWindow:

Word::Window* pWindow = NULL;
HRESULT hr = AccessibleObjectFromWindow(hwnd, OBJID_NATIVEOM, __uuidof(Word::Window), (void**)&pWindow);

That’s it!  We now have our Word::Window COM Object.  From this object we can obtain the Word::Application and Word::Document objects, allowing us full interaction with the active document.  So with just a few lines of code, we now have access to automate a word 2007 document.

Full source code:

#include <windows.h>
#include <oleacc.h>
#include "msword.h"

static BOOL EnumChildProc(HWND hwnd, LPARAM)
{
	WCHAR szClassName[64];
	if(GetClassNameW(hwnd, szClassName, 64))
	{
		if(_wcsicmp(szClassName, L"_WwG") == 0)
		{
			//Get AccessibleObject
			Word::Window* pWindow = NULL;
			HRESULT hr = AccessibleObjectFromWindow(hwnd, OBJID_NATIVEOM, __uuidof(Word::Window), (void**)&pWindow);
			if(hr == S_OK)
			{
				//Word object is now in pWindow pointer, from this you can obtain the document or application
				Word::_Document* pDoc = NULL;
				pWindow->get_Document(&pDoc);
			}
			return false;     // Stops enumerating through children
		}
	}
	return true;
}
int main( int argc, CHAR* argv[])
{
	//The main window in Microsoft Word has a class name of OpusApp
	HWND wordWindow = FindWindow(L"OpusApp", NULL);

	//Use the EnumChildWindows function to iterate through all child windows until we find _WwG
	EnumChildWindows(wordWindow, (WNDENUMPROC) EnumChildProc, (LPARAM)1);

	return 0;
}

The logic to find the correct window can be changed for multiple instances of Word.  Also, you must have the Word type library imported to use the Word COM API.  We’ll leave those two for another topic on another date. Check back later in the week for a follow up post on how to access Microsoft Excel 2007 in the same manner.

Useful Links for this post:

• AccessibleObjectFromWindow Documentation
• Using Visual C++ to Automate Office
• EnumChildWindows Documentation

Key phrases: Accessing Word 2007 COM object using AccessibleObjectFromWindow, Automating Word 2007 with Microsoft Active Accessibility MSAA

Over the next few months, I will be interacting with Microsoft Access, Word, and Excel 2007 through Microsoft Active Accessibility (MSAA) in C++. As my journey progresses, I will be posting the neat little tricks and painful quirks that I run into along the way. To start, here are a few resources you can use to read up on Microsoft Active Accessibility.

• Microsoft’s documentation on IAccessible interface
• Sara Ford’s Weblog on Accessibility
• User Interface Element References for Control in Accessibility

Over the past 6 months, I used MSAA to develop against Microsoft Access 2003.  Although it was a painful process to get working, the end result gives quite a bit of flexibility in automating Access.  That being said, there are still a lot of hurdles to overcome, and Accessibility has definitely left many things to be desired.  In the next few weeks I will be posting about my first impressions of Accessibility and it’s inconsistencies.