Installing a Vista Office 2007 developed XLA to XP office 2003 machine

[Ed Sowell]

When I do this I get an error saying it can't find object or library for
CommandBar Menu. My guess is that the XLA file has a reference to the
earlier Office DLLs. How do I make it "let go" of the newer version DLLs and
find the proper library in the Vista/Office 2007 environment?

Ironically, I originally developed most of this XLA under XP/Office 2003,
then migrated to Vista/Office 2007. Unfortunately, I still have to be able
to deploy to an XP environment.

TIA

Ed

 

[Dave Peterson]

I'd try opening the offending xla file in xl2007.
Open the VBE
Select that addin's project
Tools|references
and remove any that are checked -- but make a not of them.
Save this file (as a different name???)

Open the new file in xl2003
Off to the VBE
And select the equivalent references
Save this file

Close xl2003, reopen xl2003 with that addin to see if it worked.

 

[exceluserforeman]

Dave Petersen answer might work. I cannot test this as I do not have 2007.
However, I do not think you can go "backwards". Like in other Excel
versions, it is difficult to go backwards unless you do not implement any new
references that are only available in the newer version. Use basic coding
that you did in 2003 into 2007 so that it is on a more campatible level.

You are heading for incompatibility problems that may not appear until a
certain combination occurs.
Also, I think, if you use Excel on 64 bit OS back to Excel on NTFS, it might
also cause errors (not sure).

PS You might have to "double-code" ie one for 2007 and one for 2003. Use
code to check the version and OS. This will ensure compatibility. Also, I see
the Mac name and you should also implement code for both platforms ie PC and
Mac if you expect the other platform ie PC, may be used. Try not to use
Functions as they just eat up memory.
Please note - I am not an expert.

 

[Ed Sowell]

Dave,

This procedure ALMOST worked. After removing all the ones from the
Vista/Xl2007 configuration and moving it to XP/Xl2003 it successfully found
everything except MS Word object lib. I then looked at a older version that
I originally developed on XP\Xl2003 and saw that it was using MS Word 10 Obj
Lib which maps to C:\program Files\Microsoft\Office10\MSWORD.OLB. So I tried
checking that in the VBE References dialog. No joy. It still insisted it
needed MS Word 12, which it again labeled as Missing. But, I found that XP
does have a C:\program Files\Microsoft\Office12 directory, albeit without
MSWORD.OLB. So I copied MSWORD.OLB from my Vista Office12 directory over the
the XP Office12 directory, and it works!

Still, I feel a bit uneasy about this. My gut feeling is there is no reason
my code should not work entirely under XP/Xl2003. While I have aded a lot of
code since moving to my Vista machine, my coding style has not changed and I
have not added any bells and whistles so far as I know. And, if were truely
OK to be using Office12\MSWORD.OLB with Xl2007 under Vista, why doesn't
Miscrsoft put it there?

Ed

 

[Dave Peterson]

I don't have any idea how MSWord works. You may want to ask this in one of the
MSWord forums.