Re: GetObject Error 13 Type mismatch

On my home computer (which still works fine), I changed it to
"Word.Document.12", and the code still executes fine. Therefore if the
install of Excel 2007 changed the class names on the office computer,
shouldn't the change to 12 on my home computer have failed?

"Stuart McCall" wrote:

"samaclau" <samaclau@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:D3075AF6-79C3-4D81-8B42-CC8B2B7D759A@xxxxxxxxxxxxxxxx

Thank you for your reply. Unfortunately I am not at the computer that is
giving me a problem, so I can't test if removing the "Word.Document"
argument
solves the problem. The code has been working fine as is for a year. It
also works fine on my home machine as well. All current Microsoft updates
have been applied to both computers. It seems to me that the GetObject
definition has changed somewhere, and what I am trying to find out is how
to
change it back to the way it was. I don't know if that means that I need
to
point to a different library, or the registry needs a change, or something
else. I am referencing all the same libraries and in the same order on
both
computers, however one works and one doesn't. I really appreciate your
help
in this matter.

Well I'm sort of clutching at straws here, but I think the installation of
the Excel trial is not a red herring. Something to try: on the affected
computer, change "Word.Document" to "Word.Document.12". If that works, then
definitely remove "Word.Document" altogether. What this probably means (if
I'm right) is that the Excel install has changed the class names of all
Office apps. This is a bit naughty, but then we are talking Microsoft...



.

Relevant Pages
Loading