KB960715 Kills ActiveX Support in Access 2003...

at least for the MS Hierarchal Grid Control. Haven't tested for other
possible failures. Two consulting clients on automatic updates that use
Access as a front end for SQL reported failures. Uninstalling KB960715 fixed
the problem - until the next automatic update installation.

Any clues on how to permanently outlaw the installation?

This may indicate that the system doesn't have the latest version of that control.
No, but Excel doesn't ship with the affected control. So, if it is present,
then *in theory* either VB6, Project, Frontpage or a third party application
containing the control must be installed. (In the latter case the third party
involved should have provided a patch by now.)

Put another way, that macro wouldn't run on a machine that only had Excel
installed, regardless of whether KB960715 is installed or not.

It's possible that there is some other Microsoft software which ships this
control, in which case it should be straightforward to persuade MS to ship a
corresponding update. However, we'll need to identify the software involved first.

Hello , I am facing same situation on Excel 2003.
08-070 forces developpers to apply KB926857.
But KB926857 can't be applied on the machines which do not have VB 6 IDE
envirionment.

An exe compiled on a machine with KB926857 can be used on a machine without
KB926857.
But a .xls files developed on a machine with KB926857 can not be used on a
machine without KB926857. It causes "Compile Error - Invalid Object".
The difference between exe and xls is that xls is not a compiled object.
So is Access 2003 file, I think.

Microsoft seems to forget to think about the case of Office VBA.

There are versions for Office Project and Office Frontpage here:

<http://www.microsoft.com/technet/security/bulletin/ms08-070.mspx>

http://www.microsoft.com/technet/sec.../ms08-070.mspx

*Theoretically* the controls in question won't be present unless the machine has
VB6, Project or Frontpage installed, or unless a third-party application has
installed them. If someone can demonstrate otherwise, I'll happily assist in
bringing this to Microsoft's attention.

Harry.

Thank you for Harry.

I forgot to tell you that this is the last case of you have discribed.
I am a third party who has shiped a vb6 .exe and a .xls macro.

Even though I provide a patch files extracted from KB926857,
an Excel macro occurs 'Invalid Object' error.

It dissolves by using KB957924 , instead of KB926857.

KB926857 might have bugs about that.
An article of Japnese MSDN Forum shows this:
(I don't know how to translate the article into English.)
http://social.msdn.microsoft.com/For...-52a092c67fde/

KB957924 includes KB926857, so if that solves your problem, OK. I'm not sure
why that would make any difference, but I'm not an ActiveX expert. If you need
any additional assistance in how you should be packaging the updated components,
I imagine there's an appropriate newsgroup.

Harry.