Msworld9.old ok but not Mso9.dll

F

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 :)
 
T

Tom Winter

Francois said:
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 :)

Honestly, I am at a loss at this point. The references ought to "transfer"
over to Word XP just fine. Why don't you e-mail me the Word file
(unprotected) and I'll see if I can figure it out. I've got all the versions
of Word back to 6.0 that I can test under.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top