Forcing XP to "forget" Excel 11.0 Object Library and use 9.0 inste

[tbd]

Greetings,
I'm a programmer trying to compile for a Win2K target w/MS Excel 9.0
Object Library (Excel9.olb). My XP development station wants to use MS Excel
11.0 Ohject Library during compile, and the ActiveX calls aren't working on
target.

I think "late binding" is how others deal with this, but my programming
language (LabVIEW) doesn't provide for late binding.

Q. Is it possible for Windows XP to "forget" the Excel 11.0 library and use
the 9.0 library instead?

Cheers!

 

[Norman Yuan]

Remove Excel2003 and install Excel2000?

 

[tbd]

Hi Norman,
Thanks - that's a very good idea! If I were home with both CDs I'd
follow your advice, but (unfortunately) my employer controls software pretty
tightly. I don't have the Office 2000 installation disks and even if I did,
it looks like Excel 2003 is part of an integrated Office 2003 installation(?)
Anyway it would be an ordeal just to obtain the 2000 and 2003 software ( I'd
have to restore the 2003 version after) and there's always the chance of
breaking something along the way. Still, I'll remember you suggestion for
when this happens again (at home.)

Cheers!

 

[Norman Yuan]

It is commonly regarded as best practice to develop against oldest targeting
application when you intend to make your project work with multiple versions
of that application. The other option is to use late binding when doing
Office app automation, so you do not need to set reference to Excel Object
Library (of course you still have to make sure only use features of that
app, which are available to all targeting versions).