Msword.olb and Msword9.olb

[Francois]

Hi,

I have a problem : I write macros VBA on Word 2000 and in a PC full XP
(Office XP Pro, Win XP...), it doesn't works because of dll missed. I think
it's Msword9.olb (in Word 2000) and Msword.olb (in Word XP) whitch is the
source of the problem. I can't test it because this problem becomes on
costumers' PC.

What can I do to pass this problem and to make macros whitch works on the 2
systems ?

A solution is to make 2 files : 1 for Word 2000 and 1 for Word XP but for
it's not good for maintenance...

Is there a service pack whitch fix this problem ?

Thanks for your answer.

Francois

 

[Tom Winter]

You need to explain more of what doesn't work.

You need to ensure that you are referencing the type libraries for the
OLDEST version of Office that you want to support (in this case, it appears
to be Office 2000). That means you have to have Office 2000 on your
development machine.

These articles explain things well:
http://support.microsoft.com/default.aspx?scid=kb;EN-US;244167
http://support.microsoft.com/default.aspx?kbid=242375

 

[Francois]

Hello Tom,

I'll try to be more comprehensive :
I've developped macros in a document Word on Office 2000 and if I check the
VBA
references in this document I see 4 dll referenced : VBA, OLE Automation,
Mso9.dll and msword9.olb. Those references are the default references...
In one off my customers, whitch has Office XP, Mso9.dll and msword9.olb
don't exist => Compilation error...
The code is protected so he can't change the references.

What can I do to correct it ?

thanks

Francois

(and sorry for the mistakes I have made in english )

 

[Tom Winter]

Word should automatically "upgrade" those references to work with the
version of Office on the customer's computer. (Search through the newsgroups
for more discussions on this topic.) Are you sure the compilation error is
because of the references? Do you trust the customer enough to send him an
unprotected version so he can hit DEBUG when the error pops up and then see
if its really some line of code that is causing the error? Do you have
access to Office XP so you can test it yourself?

 

[Francois]

Hello mark,

Thank you for your answer.
I think if I don't find any other solution, I will have to do this. But in
consequence, I will have to use 2 sorts of documents : those whitch works
with Office 2000 and the others with Office XP... not really fun for the
different costumers (I hope the future version of office will not oblige me
to do this).

Francois

 

[Jean-Guy Marcil]

Hi François,

As Tom wrote in his reply to your post, you should not have to compile in XP
and therefore end up with two document to maintain.

There is something else going on here. I have written macros in Word 97 that
run fine on Word XP... And I did not recompile and saved the result in an XP
document, so to speak.

You have to find out exactly what part of the code causes the problem.
If you are considering recompiling under XP, that means you have access to
an XP machine, right? If so, debug your code step by step to see where the
error is generated.

--
Cheers!
_______________________________________
Jean-Guy Marcil - Word MVP
(e-mail address removed)
Word MVP site: http://www.word.mvps.org

 

[Francois]

Hello Tom,

Thank you for your answer.
That's right, I'm not sure the the compilation error is because of the
references, but I think it's. I will send an unprotected version to the
customer to see if it is really that (I don't think he's a genius in
informatic, he only want that's work ).
Let's try it.

Francois

 

[Tom Winter]

"Jean-Guy Marcil" wrote...

There is something else going on here. I have written macros in Word 97 that
run fine on Word XP... And I did not recompile and saved the result in an XP
document, so to speak.

<snip>

Heck, I've written macros way back in Word 6.0 that got auto-converted into
pseudo-VBA by Word 97 years ago and that still work under Word 2003!

 

[Francois]

Hello everybody, (particular Tom)

For Tom :
I have tested the problem with an unprotected version of the document (I
have sent it to my customer), and it's effectively a compilation error
because of Mso9.dll missed.

For Everybody, I explain the problem :
I write macros VBA on Word 2000 and in a PC full XP (Office XP Pro, Win
XP...) in one of my customer, it doesn't works because of dll missed whitch
is finaly Mso9.dll. If I check the VBA references in this document in my
configuration (Office 2000, W98) I see 4 dll referenced : VBA, OLE
Automation, Mso9.dll and msword9.olb. Those references are the default
references...

In one of my customers whitch has Office XP, Mso9.dll and msword9.olb
don't exist => Compilation error... because Mso9.dll is missed (only it).
The code is protected so he can't change the references.

What can I do to pass this problem and to make macros whitch works on the 2
systems ?
A solution would be to make 2 files : 1 for Word 2000 and 1 for Word XP but
it's not good to maintain
So, Is there a service pack whitch fix this problem or a method to "prepar"
the VBA environment ?

Thanks for your answer.

Francois

Ps : sorry for the mistakes
Ps2 : I have created a new News.