MS Run-time error '-2147023174 (800706ba) 1

[thirty4d]

I was testing a function per Q159328 - ACC: Example: Mail Merge a MS Access 97 Query with Word 97 document.

I would like to point out that I am using Windows 2000 Professional.

Yesterday I got it to work but this morning when I tried the code again in the Debug window, aside from taking forever and when I did the Ctl Alt + Delete to stop the code from running this was the message that I received:

Run-time error '-2147023174 (800706ba)':

Automation Error The RPC server is unavailable

Thanks!

 

[Databaseguy]

Read the following. I had similar probs & this fixed it.


SYMPTOMS
While running code that uses Automation to control Microsoft Word 97, Word 2000, or Word 2002, you may receive one of the following error messages:

Run-time error '-2147023174' (800706ba)
Automation error
-or-
Run-time error '462': The remote server machine does not exist or is unavailable



CAUSE
Visual Basic has established a reference to Word due to a line of code that calls a Word object, method, or property without qualifying it with a Word object variable. Visual Basic does not release this reference until you end the program. This errant reference interferes with automation code when the code is run more than once.



RESOLUTION
Modify the code so that each call to a Word object, method, or property is qualified with the appropriate object variable.



STATUS
This behavior is by design.



MORE INFORMATION
To automate Microsoft Word, you establish an object variable that usually refers to the Word Application or Document object. Other object variables can then be set to refer to a Selection, a Range, or other objects in the Microsoft Word object model. When you write code to use a Word object, method, or property, you should always precede the call with the appropriate object variable. If you do not, Visual Basic uses a hidden global variable reference which it sets to the currently running instance. If Word is shutdown, or if the declared object variable is released, the hidden global variable will now reference an invalid (i.e., destroyed) object. When running the automation code again, calls to this hidden object variable will fail with the aforementioned error.

The following steps illustrate how to reproduce this problem, and how to correct it.

Steps to Reproduce Behavior
Start a new Standard EXE project in Visual Basic. Form1 is created by default.


Click References from the Project menu and check "Microsoft Word 8.0 Object Library" for Word 97. For Word 2000, check "Microsoft Word 9.0 Object Library." For Word 2002, check "Microsoft Word 10 Object Library."


Place a CommandButton on Form1.


Copy the following code to the Code Window of Form1:


Option Explicit

Private Sub Command1_Click()
Dim oWord As Word.Application
Dim oDoc As Word.Document
Dim oRange as Word.Range

Set oWord = CreateObject("Word.Application&quot
With oWord
.Visible = True
.Activate
.WindowState = wdWindowStateNormal
End With

Set oDoc = oWord.Documents.Add
MsgBox "Document open", vbMsgBoxSetForeground
With oDoc
.PageSetup.LeftMargin = InchesToPoints(1.25)
End With

' This example inserts text at the end of section one.
Set oRange = ActiveDocument.Sections(1).Range
With oRange
.MoveEnd Unit:=wdCharacter, Count:= -1
.Collapse Direction:=wdCollapseEnd
.InsertParagraphAfter
.InsertAfter "End of section."
End With

With oDoc
.Saved = True
End With

Set oRange = Nothing
Set oDoc = Nothing
oWord.Quit
Set oWord = Nothing
End Sub
On the Run menu, click Start or press the F5 key to start the program.


Click the CommandButton. No error occurs. However, a reference to Word 97, 2000, or 2002 has been created and has not been released.


Click the CommandButton again and note that you receive the error previously described.

NOTE: The error occurs because the code refers to the InchesToPoints Method without preceding the call with the oWord object variable.


Stop the project and change the following line:


.PageSetup.LeftMargin = InchesToPoints(1.25)
-to-
.PageSetup.LeftMargin = oWord.InchesToPoints(1.25)
Run the program again. Then, click the CommandButton. No error occurs.


Click the CommandButton again and note that you receive the error.

NOTE: The error occurs because the code refers to the ActiveDocument Section one's Range object without preceding the call with the oWord object variable.


Stop the project and change the following line:


Set oRange = ActiveDocument.Sections(1).Range
-to-
Set oRange = oWord.ActiveDocument.Sections(1).Range
Run the program again. Note that you can run the code multiple times without error.


When building a Visual Basic project automating Word, if your project has a reference to the Microsoft Word 8.0, 9.0, or 10.0 Object Library, sample code for the objects, methods, and properties of the Word Object Model is available from the Word Help file. When the cursor is over a key word in your code, you will see any applicable Help text by pressing the F1 key.

The sample code in the Help topic will be the Microsoft Word Visual Basic for Applications code. It will not show the object references that your Visual Basic code requires. You will need to add the qualifiers as appropriate.



REFERENCES
For additional information, please see the following articles in the Microsoft Knowledge Base:

Q178510 PRB: Excel Automation Method of Object '_Global'Failed
Q167223 Microsoft Office 97 Automation Help File Available
For additional information about the Automation of Office applications, click the article number below to view the article in the Microsoft Knowledge Base:
Q222101 HOWTO: Find and Use Office Object Model Documentation
Or visit the following Microsoft Web site:

http://support.microsoft.com/support/officedev/automation.asp

Tyrone Lumley
augerinn@gte.net

http://server47.hypermart.net/databaseguy

 

[thirty4d]

Hello Databaseguy:

Thank you so much for all these information. Before I do your instructions, one more question though.

On the Tools/Options/Advanced: DDE Operations

Ignore DDE Requests and Enable DDE Refresh are both checked, does that make any difference?

Thanks a million

 

[Databaseguy]

DDE is another way of going about automation. Although I don't claim to understand it, I don't think we're using DDE when using VBA Automation. So, it shouldn't make any difference. Tyrone Lumley
augerinn@gte.net

http://server47.hypermart.net/databaseguy

 

[thirty4d]

Hello Databaseguy,

Thanks again for the info but please do check back as I want to let you know how I did after using your new code..


Thanks again

 

[Databaseguy]

Will do !!!

Say, Monday ???? Tyrone Lumley
augerinn@gte.net

http://server47.hypermart.net/databaseguy

 

[thirty4d]

Sounds good!!!

BTW: Congratulations! Databaseguy on being voted TipMaster of the Week! last week?

 

[thirty4d]

Hello Databaseguy,

Hey! It seemed I got it work.

Per your instruction I created a standard exe in VB6.

When I clicked on the command button, a message box displayed "Document Open" also MS Word blank document.

Damn! it feels good not to get an error for a change .

What's next?

Thanks a bunch for giving such a great instructions!