Tools/References/Microsoft Word 10.0 Object Library vs 11.0

[Guest]

Hello,

(I can go a year without asking a question, then it seems like I'm asking
questions weekly... sorry!)

Anyway, I wrote an additional feature for a client which works perfectly for
me and for all the people/machines in one of my client's departments, but not
the other. It gathers a few separate Word documents and combines them into
one Word document - all within the a form's code in Access. The only
difference is that in the department where is doesn't work, they have Office
XP, and the department it does work in has Office 2003. We believe we've
narrowed it down to the fact that the non-working ones have the Microsoft
Word 10.0 Object Library, while the working ones have 11.0. I'm really not
doing anything fancy in the code. Is there a way to "update" the library
without the other department having to purchase and install Office 2003?

Thanks,
April

 

[Guest]

Do they have Access 2003 or are you supplying the runtime?
Are you giving them an MDB or MDE?

You could set a reference to the 10.0 library in the version you roll out to
the Office XP users.

I'm not sure about this but, I think you could set a reference to both
libraries (with 11.0 before 10.0 in the list) then it will use 11.0 if it can
but fall back on 10.0 if it cannot. I've never done it myself but I'm sure I
read this somewhere a while back.

Steve

 

[Guest]

SteveM,

They have Office (incl. Access) 2003 on most machines, but Office (incl
Access) XP on a handful. I supply them with the .mdb (two actually, one for
interface, one for backend data). I can only set a reference to the 10.0
Library from an Office XP machine, as mine (an Office 2003) doesn't have it.
(Yes, I do believe you are correct that I could add a reference to both, but
Access gives an ugly error if a Library is missing on a machine; so error on
missing 11.0 on the Office XP machines and error on missing 10.0 on the
Office 2003 machines.) I also supply them with "updated" frontend interface
..mdb's on a fairly often basis, so having them have to manually change to the
10.0 Library every time will be too much for them.

However, I have since been doing more testing with them (over the phone, as
I am remote from their location) and it seems they may have been using an
"old" version of the frontend interface, as opposed to the one I just sent
them. So, the current modified scenario is that the new frontend interface
DOES work with either 10.0 or 11.0; but they still don't want to have to make
this Library change every time I make an update for them.

As it stands, I may have talked them into upgrading the remaining machines
to Office 2003.

Thanks, though, for the response...
April

 

[Guest]

Well, you could set the reference in code...

Search to see which one exists on the machine and then set the reference to
the appropriate library.

Steve