Fix Word 2013 Automation from a VB6 Application
Question details
Troubleshoot a VB6 application that no longer automates Word after an upgrade from Word 2010 to Word 2013.

- Product
- Microsoft Word 2013 and Visual Basic 6
- Device & OS
- not provided
- Scenario
- A VB6 application uses the Word.Application COM class to automate Microsoft Word.
- Observed behavior
- Automation may fail after Word 2013 is installed, including when the application uses GetObject.
Record the exact VB6 error number, message, and line of code that fails. Check whether Word 2013 opens normally and whether an instance is already running when the application calls GetObject.
Test Word automation with late binding
Use this test to distinguish a failure to attach to a running Word instance from a failure to create one.
GetObject(, "Word.Application") attempts to attach to a running Word instance; it does not start Word if none is available. Late binding uses an Object variable instead of a version-specific Word object type.
In the VB6 editor, inspect the GetObject call and record Err.Number and Err.Description when it fails.
Start Word 2013 manually, then run the application and test GetObject(, "Word.Application") again.
In a small VB6 test, declare the Word variable As Object and try CreateObject("Word.Application") if attaching fails. Capture the error number and description if creation also fails.
If CreateObject succeeds but GetObject fails, review whether a suitable Word instance is running under the same user and permission context. If both fail, investigate registration and installation.

Check Word references, registration, and permissions
Use these checks if late binding fails or the application depends on a Word type library.
Edit Word Documents with WPS Office
For everyday document work, WPS Office is a free, lightweight alternative with a familiar interface and support for common Word formats, making it easier to move existing documents. It does not fix Microsoft Word COM automation or guarantee compatibility with VB6 automation code.

Frequently Asked Questions
Why does GetObject fail when Word is not open?
GetObject(, "Word.Application") tries to attach to a running Word instance. If no suitable instance is available, test CreateObject("Word.Application") to start one instead.
Where can I check the Word reference in VB6?
In the VB6 editor, open Project > References and look for a missing Microsoft Word reference. Projects using early binding may need a valid Word 2013 object library reference.
Does 64-bit Word automatically prevent VB6 automation?
Not necessarily. Word is an out-of-process COM server, so bitness alone does not establish the cause. Check any 32-bit or 64-bit in-process DLLs used by the application and record the exact automation error.
Can WPS Office fix a Word.Application COM error?
No. WPS Office can be an alternative for editing Word documents, but a Word.Application COM error requires troubleshooting Microsoft Word, its registration, or the VB6 application.




