Anyone experienced this?
Setup: a AC2003 app which includes a reference to "Microsoft Office 11
Object Library" (for CommandBars, etc.)
Install Office 2007 Compatibility Pack (O2k7CP) on Developers machine, so
he
can read do***ents sent by Office 2007 users who won't/don't save in older
file formats.
The AC2003 app now has reference to "Microsoft Office 12 Object Library".
If this file is distributed to a AC2003 user who does NOT have O2k7CP,
they
will get a "..you have a broken reference to MOS.dll version 2.4 " error
at
startup.
Verified Workarounds (without changing to Late binding):
1) have user install O2k7CP
or
2) developer uninstalls O2k7CP, changes now missing Office 12
reference
back to Office 11 and redistributes.
It might be worth mentioning that I'm not exactly sure when the reference
changed from 11 to 12. It may not have happened automatically when O2k7CP
was installed, it may have required a file rebuild (im****t all objects
into
a new blank mdb) to trigger the 'change'. I haven't had the time to
attempt
a change re-trigger.
I assume this would also apply to AC2002/XP, since O2k7CP can be used with
that as well.
This caught me by surprise late Friday and I was a little ticked at the
wholesale reference substitution with no warning whatsoever, although I
can
see how it would be necessary in order for O2k7CP to work. It was not the
most pleasant way to end a week :-)
--
George
|
