Strange Automation Issue

[Neil Ginsberg]

I have a strange situation with my Access 2000 database. I have code in the
database which has worked fine for years, and now all of a sudden doesn't
work fine on one or two of my client's machines. The code opens MS Word
through Automation and then opens a particular Word doc. It's still working
fine on most machines; but on one or two of them, the user is getting an
Automation Error. The code used is as follows:

Dim objWord As Word.Applicatio n
Set objWord = New Word.Applicatio n
objWord.Documen ts.Open FileName:=strFi lename, _
ConfirmConversi ons:=False, _
ReadOnly:=False , _
AddToRecentFile s:=False, _
Revert:=False, _
Format:=gcon_wd OpenFormatAuto 'this is global constant with
Word constant value

The Automation Error occurs on the third line, when trying to open the
document (the document does exist, so that's not the problem).

Even stranger than the fact that the problem's only happening on two out of
several dozen machines, is the following. I have a pared-down copy of the
database, that users use to take on the road with them and show to clients.
The pared-down version (call it "App B") was taken from the original (call
it "App A") with some functionality removed. Regarding the above code that's
failing, both App A and App B are identical, and both have the same
references.

Now, here's the really strange part.

On one computer that's having problems, App A fails in the above code. On
the other computer that's having problems, App A works fine in the above
code, but App B fails in that code. So, in the second case, with the same
computer and two identical sets of code, one set fails, the other doesn't.

I've looked at backup copies to see if it was a corruption issue, and
haven't seen any difference. And, as noted, this code has been in place for
years without problems, until just the other day when these problems started
happening.

All of the users have MS Office and the database application installed on
their C drives.

Any assistance would be appreciated.

Thanks!

Neil

[Geoff]

> the user is getting an Automation Error.

Neil

I don't know if this might help pinpoint the problem.

Have you written an error handler to display the
automation error using the vbObjectError constant?

If you need it, the following information relates to the
vbObjectError constant:

1. Subtracting vbObjectError from Err.Number will
indicate the error as defined by the server application.

2. However, if subtracting vbObjectError from Err.Number
results in a number outside the range 0 - 65535, the
error is a VBA error.

Therefore, your error handler might look like:

' Remove the constant added by the server application:
MyError = Err.Number - vbObjectError

' Is the result in the range 0 - 65535?
If MyError > 0 and MyError < 65535 then

Msg = "The object you accessed assigned this number to " & _
"the error: " & MyError & ". The originator of " & _
"the error was: " & Err.Source & ". Press F1 to " & _
"see the originating applications' help topic."

Else ' It's a VBA error:

Msg = "This error " & Err.Number & " is a VBA error. " & _
"Press Help button or F1 for VBA Help topic on " & _
"this error."

End if

Msgbox Msg, , "Object Error", Err.Helpfile, Err.HelpContext
Obviously, this doesn't solve your problem, but it may
help you identify it.

HTH
Geoff

[TC]

*What* automation error?

TC
"Neil Ginsberg" <nr*@nrgconsult .com> wrote in message
news:5t******** *********@newsr ead3.news.pas.e arthlink.net...

I have a strange situation with my Access 2000 database. I have code in the database which has worked fine for years, and now all of a sudden doesn't
work fine on one or two of my client's machines. The code opens MS Word
through Automation and then opens a particular Word doc. It's still working fine on most machines; but on one or two of them, the user is getting an
Automation Error. The code used is as follows:

Dim objWord As Word.Applicatio n
Set objWord = New Word.Applicatio n
objWord.Documen ts.Open FileName:=strFi lename, _
ConfirmConversi ons:=False, _
ReadOnly:=False , _
AddToRecentFile s:=False, _
Revert:=False, _
Format:=gcon_wd OpenFormatAuto 'this is global constant with
Word constant value

The Automation Error occurs on the third line, when trying to open the
document (the document does exist, so that's not the problem).

Even stranger than the fact that the problem's only happening on two out of several dozen machines, is the following. I have a pared-down copy of the
database, that users use to take on the road with them and show to clients. The pared-down version (call it "App B") was taken from the original (call
it "App A") with some functionality removed. Regarding the above code that's failing, both App A and App B are identical, and both have the same
references.

Now, here's the really strange part.

On one computer that's having problems, App A fails in the above code. On
the other computer that's having problems, App A works fine in the above
code, but App B fails in that code. So, in the second case, with the same
computer and two identical sets of code, one set fails, the other doesn't.

I've looked at backup copies to see if it was a corruption issue, and
haven't seen any difference. And, as noted, this code has been in place for years without problems, until just the other day when these problems started happening.

All of the users have MS Office and the database application installed on
their C drives.

Any assistance would be appreciated.

Thanks!

Neil

[Neil Ginsberg]

"Run-time error '-2147023067 (80070725)': Automation error."

"TC" <a@b.c.d> wrote in message news:1067480554 .540605@teuthos ...

*What* automation error?

TC
"Neil Ginsberg" <nr*@nrgconsult .com> wrote in message
news:5t******** *********@newsr ead3.news.pas.e arthlink.net...

I have a strange situation with my Access 2000 database. I have code in

the

database which has worked fine for years, and now all of a sudden doesn't work fine on one or two of my client's machines. The code opens MS Word
through Automation and then opens a particular Word doc. It's still

working

fine on most machines; but on one or two of them, the user is getting an
Automation Error. The code used is as follows:

Dim objWord As Word.Applicatio n
Set objWord = New Word.Applicatio n
objWord.Documen ts.Open FileName:=strFi lename, _
ConfirmConversi ons:=False, _
ReadOnly:=False , _
AddToRecentFile s:=False, _
Revert:=False, _
Format:=gcon_wd OpenFormatAuto 'this is global constant with
Word constant value

The Automation Error occurs on the third line, when trying to open the
document (the document does exist, so that's not the problem).

Even stranger than the fact that the problem's only happening on two out

of

several dozen machines, is the following. I have a pared-down copy of the database, that users use to take on the road with them and show to

clients.

The pared-down version (call it "App B") was taken from the original (call it "App A") with some functionality removed. Regarding the above code

that's

failing, both App A and App B are identical, and both have the same
references.

Now, here's the really strange part.

On one computer that's having problems, App A fails in the above code. On the other computer that's having problems, App A works fine in the above
code, but App B fails in that code. So, in the second case, with the same computer and two identical sets of code, one set fails, the other doesn't.
I've looked at backup copies to see if it was a corruption issue, and
haven't seen any difference. And, as noted, this code has been in place

for

years without problems, until just the other day when these problems

started

happening.

All of the users have MS Office and the database application installed on their C drives.

Any assistance would be appreciated.

Thanks!

Neil

[Neil Ginsberg]

In my case, Err.Number = -2147023067 and vbObjectError = -2147221504.
Subtracting the second from the first I get 198437, which according to your
notes means it's a VBA error. I'm not sure where that gets me, since the VBA
code hasn't changed years and it started being problematic a couple of days
ago. Any ideas?

Thanks,

Neil
"Geoff" <ge***@nospam.f or.me.com> wrote in message
news:bn******** **@newsg1.svr.p ol.co.uk...

the user is getting an Automation Error.

Neil

I don't know if this might help pinpoint the problem.

Have you written an error handler to display the
automation error using the vbObjectError constant?

If you need it, the following information relates to the
vbObjectError constant:

1. Subtracting vbObjectError from Err.Number will
indicate the error as defined by the server application.

2. However, if subtracting vbObjectError from Err.Number
results in a number outside the range 0 - 65535, the
error is a VBA error.

Therefore, your error handler might look like:

' Remove the constant added by the server application:
MyError = Err.Number - vbObjectError

' Is the result in the range 0 - 65535?
If MyError > 0 and MyError < 65535 then

Msg = "The object you accessed assigned this number to " & _
"the error: " & MyError & ". The originator of " & _
"the error was: " & Err.Source & ". Press F1 to " & _
"see the originating applications' help topic."

Else ' It's a VBA error:

Msg = "This error " & Err.Number & " is a VBA error. " & _
"Press Help button or F1 for VBA Help topic on " & _
"this error."

End if

Msgbox Msg, , "Object Error", Err.Helpfile, Err.HelpContext
Obviously, this doesn't solve your problem, but it may
help you identify it.

HTH
Geoff

[TC]

I found a couple of posts about this error: both in German! Here's one,
translated by altavista:

"When responding Word from ACCESS (Office 97) out I have the problem that I
get an automation error from ACCESS. The complete error message reads: Run
time error -2147023067 (80070725) Automasierungfe hler Incompatible version
of the RPC Stub The common to the fact is that the program on some computers
does not laeueft and on others. On all computers NT 4,0 with service luggage
6a and Office 97 with SP2 runs. I packed some often needed functions into a
class. In this class Word is initalisiert and assigned as object of a
Membervariablen [ set Word=CreateObje ct"Word.Applica tion")..]. If the Word
object to access, hails it is now tried above error message e.g.
oWord.ChangeFil eOpenDirectory sPath. In addition, with each arbitrary other
Word function gives it this message. I have to define tried "oWord" as
Public, but that did not also help me. Does someone have one perhaps taps as
I this error to repair can?"

Ok, that was fun! Now let's try something else.

Are you sure the error occurs on the .Open call? It doesn't occur on the New
Word.Applcation ?

Perhaps try:

set objword = createobject ("word.applicat ion")

MS says: "When creating an instance of an Microsoft Office application, use
CreateObject instead of New. CreateObject more closely maps to the creation
process used by most Visual C++ clients, and allows for possible changes in
the server's CLSID between versions. CreateObject can be used with both
early-bound and late-bound objects."

HTH,
TC
"Neil Ginsberg" <nr*@nrgconsult .com> wrote in message
news:zM******** *********@newsr ead4.news.pas.e arthlink.net...

"Run-time error '-2147023067 (80070725)': Automation error."

"TC" <a@b.c.d> wrote in message news:1067480554 .540605@teuthos ...

*What* automation error?

TC
"Neil Ginsberg" <nr*@nrgconsult .com> wrote in message
news:5t******** *********@newsr ead3.news.pas.e arthlink.net...

I have a strange situation with my Access 2000 database. I have code in

the

database which has worked fine for years, and now all of a sudden doesn't work fine on one or two of my client's machines. The code opens MS

Word through Automation and then opens a particular Word doc. It's still

working

fine on most machines; but on one or two of them, the user is getting an Automation Error. The code used is as follows:

Dim objWord As Word.Applicatio n
Set objWord = New Word.Applicatio n
objWord.Documen ts.Open FileName:=strFi lename, _
ConfirmConversi ons:=False, _
ReadOnly:=False , _
AddToRecentFile s:=False, _
Revert:=False, _
Format:=gcon_wd OpenFormatAuto 'this is global constant with Word constant value

The Automation Error occurs on the third line, when trying to open the
document (the document does exist, so that's not the problem).

Even stranger than the fact that the problem's only happening on two out

of

several dozen machines, is the following. I have a pared-down copy of the database, that users use to take on the road with them and show to

clients.

The pared-down version (call it "App B") was taken from the original (call it "App A") with some functionality removed. Regarding the above code

that's

failing, both App A and App B are identical, and both have the same
references.

Now, here's the really strange part.

On one computer that's having problems, App A fails in the above code. On the other computer that's having problems, App A works fine in the

above code, but App B fails in that code. So, in the second case, with the

same computer and two identical sets of code, one set fails, the other doesn't.
I've looked at backup copies to see if it was a corruption issue, and
haven't seen any difference. And, as noted, this code has been in

place for

years without problems, until just the other day when these problems

started

happening.

All of the users have MS Office and the database application installed

on their C drives.

Any assistance would be appreciated.

Thanks!

Neil

[Neil Ginsberg]

> Are you sure the error occurs on the .Open call? It doesn't occur on the
New

Word.Applcation ?
Yes, positive. I thought that was a bit strange myself. It also occurs if I
try to do anything else (i.e., skip the offending line), such as set the
application's Visible property to True, etc. In other Words, it creates the
object fine; but then it won't do anything with it!

Perhaps try:

set objword = createobject ("word.applicat ion")
That's the code I'm using. Wait a minute: in my message I posted other code.

OK, I may have stumbled upon something. I just noticed that the original app
I referred to as "App A" uses the code:

Set objWord = New Word.Applicatio n

whereas the pared-down app I referred to as "App B" uses:

Set objWord = CreateObject("W ord.Application ")

On the computer I have access to (via PC Anywhere), App A is working fine,
but App B isn't. So that might be something to try. (Still doesn't explain
why it would all of a sudden start having problems, when my notes show that
I changed the App A code last June -- must have forgotten that I had done
that -- but at least it's a start!)

MS says: "When creating an instance of an Microsoft Office application, use CreateObject instead of New. CreateObject more closely maps to the creation process used by most Visual C++ clients, and allows for possible changes in the server's CLSID between versions. CreateObject can be used with both
early-bound and late-bound objects."
That would actually be the opposite of what I'm finding -- that the one with
New is working, but the one with CreateObject isn't. Oh well, whatever takes
care of the problem. Will try that and see how it goes.

HTH,
Indeed!

Thanks,

Neil
TC
"Neil Ginsberg" <nr*@nrgconsult .com> wrote in message
news:zM******** *********@newsr ead4.news.pas.e arthlink.net...

"Run-time error '-2147023067 (80070725)': Automation error."

"TC" <a@b.c.d> wrote in message news:1067480554 .540605@teuthos ...

*What* automation error?

TC
"Neil Ginsberg" <nr*@nrgconsult .com> wrote in message
news:5t******** *********@newsr ead3.news.pas.e arthlink.net...
> I have a strange situation with my Access 2000 database. I have code in the
> database which has worked fine for years, and now all of a sudden doesn't

> work fine on one or two of my client's machines. The code opens MS Word > through Automation and then opens a particular Word doc. It's still
working
> fine on most machines; but on one or two of them, the user is getting an

> Automation Error. The code used is as follows:
>
> Dim objWord As Word.Applicatio n
> Set objWord = New Word.Applicatio n
> objWord.Documen ts.Open FileName:=strFi lename, _
> ConfirmConversi ons:=False, _
> ReadOnly:=False , _
> AddToRecentFile s:=False, _
> Revert:=False, _
> Format:=gcon_wd OpenFormatAuto 'this is global constant with > Word constant value
>
> The Automation Error occurs on the third line, when trying to open

the > document (the document does exist, so that's not the problem).
>
> Even stranger than the fact that the problem's only happening on two out of
> several dozen machines, is the following. I have a pared-down copy of the

> database, that users use to take on the road with them and show to
clients.
> The pared-down version (call it "App B") was taken from the original

(call

> it "App A") with some functionality removed. Regarding the above

code that's
> failing, both App A and App B are identical, and both have the same
> references.
>
> Now, here's the really strange part.
>
> On one computer that's having problems, App A fails in the above code.

On

> the other computer that's having problems, App A works fine in the above > code, but App B fails in that code. So, in the second case, with the

same

> computer and two identical sets of code, one set fails, the other

doesn't.

>
> I've looked at backup copies to see if it was a corruption issue,

and > haven't seen any difference. And, as noted, this code has been in

place for
> years without problems, until just the other day when these problems
started
> happening.
>
> All of the users have MS Office and the database application

installed on

> their C drives.
>
> Any assistance would be appreciated.
>
> Thanks!
>
> Neil

[Tom Wickerath]

Here is a KB article that might be helpful:

INFO: Translating Large Office Automation Error Values
http://support.microsoft.com/default...roduct=acc2000

It includes a link to this KB article:
INFO: Translating Automation Errors for VB/VBA (Long)
http://support.microsoft.com/default.aspx?kbid=186063
When I ran the MessageText function with the error number you reported, I get the
following result. Note: I had to change the scope of the function from Private to Public.

?MessageText(-2147023067)
Incompatible version of the RPC stub.

Hmmm....what does this helpful message mean? I conducted a search of the Knowledge Base
at:
http://support.microsoft.com/default...;EN-US;KBHOWTO

using the text returned by the MessageText function. I specified "All Microsoft Products"
and "Using: All of the words entered". I found 7 hits, one of which looks particularly
promising:

PRB: Office Automation Fails with an Incompatible RPC Stub Error
http://support.microsoft.com/default...b;en-us;320108

I think you may find the answer in the above KB article!

Good Luck, and please report your findings back to the newsgroup.

Tom
_______________ _______________ _____________

"Neil Ginsberg" <nr*@nrgconsult .com> wrote in message
news:PU******** *********@newsr ead4.news.pas.e arthlink.net...

In my case, Err.Number = -2147023067 and vbObjectError = -2147221504.
Subtracting the second from the first I get 198437, which according to your
notes means it's a VBA error. I'm not sure where that gets me, since the VBA
code hasn't changed years and it started being problematic a couple of days
ago. Any ideas?

Thanks,

Neil
"Geoff" <ge***@nospam.f or.me.com> wrote in message
news:bn******** **@newsg1.svr.p ol.co.uk...

the user is getting an Automation Error.

Neil

I don't know if this might help pinpoint the problem.

Have you written an error handler to display the
automation error using the vbObjectError constant?

If you need it, the following information relates to the
vbObjectError constant:

1. Subtracting vbObjectError from Err.Number will
indicate the error as defined by the server application.

2. However, if subtracting vbObjectError from Err.Number
results in a number outside the range 0 - 65535, the
error is a VBA error.

Therefore, your error handler might look like:

' Remove the constant added by the server application:
MyError = Err.Number - vbObjectError

' Is the result in the range 0 - 65535?
If MyError > 0 and MyError < 65535 then

Msg = "The object you accessed assigned this number to " & _
"the error: " & MyError & ". The originator of " & _
"the error was: " & Err.Source & ". Press F1 to " & _
"see the originating applications' help topic."

Else ' It's a VBA error:

Msg = "This error " & Err.Number & " is a VBA error. " & _
"Press Help button or F1 for VBA Help topic on " & _
"this error."

End if

Msgbox Msg, , "Object Error", Err.Helpfile, Err.HelpContext
Obviously, this doesn't solve your problem, but it may
help you identify it.

HTH
Geoff

[rkc]

"TC" <a@b.c.d> wrote in message news:1067486213 .516312@teuthos ...

I found a couple of posts about this error: both in German! Here's one,
translated by altavista:
<snip translation>
Ok, that was fun! Now let's try something else.

Cracked me up.

[Geoff]

Neil

Now that this thread has arrived on my machine and
notwithstanding Tom's lead in the other thread (which
perhaps offers more hope).

Word is (I believe) an application that likes to have only
one instance running - although I think I've got multiple
instances running from code before now for reasons
I've never got to the bottom of. Also, I've read some
incomprehensibl e stuff on memory not being released
when some object variables are set to Nothing after
they've been created using 'New' (even when no other
variables are pointing to the same object).

So, as you're using CreateObject, is there any mileage
in using the GetObject function first (to utilise any
running instance of Word, if Word prefers to be in
memory only once or simply to save system resources).
And, if GetObject produces error 429, then using
CreateObject?

I've seen two coding variations for the above, each of
which uses a boolean variable to leave Word running
if GetObject was successful, but quit Word if
CreateObject was successful. (I can post samples if
you want them.)

No doubt you're destroying object variables when
no longer needed by setting them to Nothing.

Presumably all Office/Windows service packs are
installed on the offending machine.

I realise this doesn't address your specific issue or
the bizarre nature of your code suddenly not
working - but HTH.

Like Tom, I'd be interested in your solution.

Regards
Geoff