KB960715 blocks msflxgrd.ocx in VBA

Discussion in 'Windows Update' started by kevin.meers, Feb 12, 2009.

  1. kevin.meers

    kevin.meers Guest

    This update (KB960715) causes a problem with the msflxgrd.ocx control
    when used in a Access 2003 application. The control gets blocked and
    you have to uninstall the update. Would appricate a fix for this as I
    am sure this is not what Microsoft intended to fix with this update.
    kevin.meers, Feb 12, 2009
    1. Advertisements

  2. kevin.meers

    chrisdev3 Guest

    I have the same problems also with MSFLXGRD.OCX. What are going to do
    now since our programs that do not work ? We have to replace flexgrid
    with different control ? Lot of clients will not accept uninstalling

    Apart from uninstalling update or executing the below, I was not able
    to find another solution till now:

    Windows Registry Editor Version 5.00
    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\ActiveX
    "Compatibility Flags"=-
    chrisdev3, Feb 12, 2009
    1. Advertisements

  3. If all of your MS and third-party applications are fully patched themselves,
    installing KB960715 shouldn't be causing any problems.

    There are only two (2) killbits set by KB960715, one for Akamai Download
    Manager and one for Research in Motion (RIM) AxLoader. Both Akamai and RIM
    have released security updates related to these killbits: Have you installed
    the appropriate update(s) yet? See the FAQ section of

    NB: KB960715 also includes the killbits in KB956391 (originally released 14
    Oct-08); cf. http://www.microsoft.com/technet/security/advisory/956391.mspx.
    Did you uninstall it, too?
    PA Bear [MS MVP], Feb 12, 2009
  4. kevin.meers

    kevin.meers Guest

    Have got all the latest updates (apart from this one as have removed
    it) and am fully patched. Not sure why it causes an issue but it does.
    Have also logged issue the Microsoft UK so fingers crossed.
    kevin.meers, Feb 12, 2009
  5. kevin.meers

    chris Guest

    We have a PAYROLL application that runs on MS Access 2003 and uses
    msdatgrd.ocx. Our customers were not able to pay their employees today.
    Thank god for this post. We told everyone to remove the update
    chris, Feb 12, 2009
  6. kevin.meers

    mik724 Guest

    I had similar issue since yesterday, and I tried re-registering the msflxgrd
    serveral times but did not fix the errors. The only solution so far has been
    to remove the KB960715. Thanks guys and let's keep posted on this issue.
    mik724, Feb 12, 2009
  7. kevin.meers

    mik724 Guest

    I am having similar problem since yesterday. I tried re-registering msflxgrd
    serveral times, but did not fix. The only solution so far is to remove the
    KB960715. Thanks guys and let's keep posted
    mik724, Feb 12, 2009
  8. http://www.microsoft.com/technet/security/advisory/960715.mspx
    -> General Information -> Frequently Asked Questions ->
    What does this update do?

    The following class identifiers relate to the CAPICOM control addressed
    in Microsoft Security Bulletin MS08-070, Vulnerabilities in Visual Basic
    6.0 Runtime Extended Files (ActiveX Controls) Could Allow Remote Code
    Execution (932349):

    Class Identifier









    See http://www.microsoft.com/technet/security/Bulletin/MS08-070.mspx for
    further details though.

    Ottmar Freudenberger, Feb 13, 2009
  9. kevin.meers

    chrisdev3 Guest

    Yes, it seems we were missing last update. KB960715 blocks msflxgrd
    older versions than (November 2008)

    http://support.microsoft.com/kb/957924 includes updates of controls
    that should be used in order not to have conflict with windows
    chrisdev3, Feb 13, 2009
  10. Found in http://forums.techarena.in/windows-update/1121231.htm:
    Posts: n/a

    Re: KB960715 blocks msflxgrd.ocx in VBA


    Yes, it seems we were missing last update. KB960715 blocks msflxgrd
    older versions than (November 2008)

    http://support.microsoft.com/kb/957924 includes updates of controls
    that should be used in order not to have conflict with windows

    Can anyone confirm this and check, if the update 960715 then can install
    without problems?

    Björn Böning, Feb 13, 2009
  11. overlooked, that this post is already posted here. Sorry!

    This may not solve this issue, because there are also users without VB6
    installed with this problem.
    Björn Böning, Feb 13, 2009
  12. kevin.meers

    mmorasan Guest

    This is exactly our problem, we have 200+ users who lost flexgrid
    functionality with the auto application of kb960715. Only our
    developer, who has VB6, was able to install the security roll up and
    continue to use flexgrid pages on our custom intranet site. Thi site
    was designed about 8 years ago and has never had an incompatibility
    with any MS security updates until now. Any thoughts on replacing the
    flexgrid component in our asp based app? Or how do we update the
    client components on the pcs? thx
    mmorasan, Feb 13, 2009
  13. Of course, this means your machines are exposed to the security vulnerability again.

    Harry Johnston [MVP], Feb 14, 2009
  14. http://support.microsoft.com/kb/957924
    There are separte Security Updates for VS based apps, see MS08-070
    for details and links.

    Ottmar Freudenberger, Feb 14, 2009
  15. And you re-enabled the vulnerability with doing so. Not a wise idea
    if you'ld ask me.

    Ottmar Freudenberger, Feb 14, 2009
  16. kevin.meers

    Aquidneck Guest

    The good news is that there's a download that brings most, if not all, the
    affected controls up to date: KB957924 is a VS6 rollup.

    The bad news is that you can't install it on a workstation that doesn't have
    VS6 installed.

    My solution was to create an empty VB6 program that utilized one of the
    controls from each of the OCX files, such as MSHFLXGD.OCX. Just the act of
    installing that empty program on the affected workstations resolved my issues
    with Access 2003.

    MS somewhat acknowledges the issue in KB932349, but doesn't provide a clear
    solution for any Office apps using VBA. I'm rather suprised and disappointed
    that they just didn't include the affected runtime files as part of the

    Al Petersen
    Aquidneck, Feb 15, 2009
  17. Harry Johnston [MVP], Feb 15, 2009
  18. kevin.meers

    Aquidneck Guest

    At least on the surface, that may solve the issue, but according to the pages
    you point to, they explicitly require the installation of Project or Front
    Page on the target workstation. For my clients, those aren't installed; they
    have the basic MSO installation of Word, Excel, PowerPoint and Access.

    Following the MS thread backwards on those pages, I still don't see a hotfix
    that corrects the problem for the base MSO installation. Tracking down
    corrections to MS oversights on hotfixes amount to non-billable hours on my
    part, and my weekends are "Heinz" weekends as it is - "catch up" on
    commitments to clients.

    Let's face it. MS dropped the ball on this one, and I'm sure left many more
    developers than me in the dark by not including the appropriate VBA runtime
    updates in KB960715. Easy enough on their part to do, and a pain in gazorkas
    for the rest of us when MS doesn't think through, and thoroughly test, the
    various hotfixes thrown at us.
    Aquidneck, Feb 16, 2009
  19. In which case, at least in theory, the controls in question shouldn't be
    installed in the first place - unless there's a third-party application
    involved, in which case it should have an update that includes the affected

    Are you able to verify that msflxgrd.ocx is installed along with a base Office
    install, without Project or Frontpage?

    Harry Johnston [MVP], Feb 16, 2009
  20. kevin.meers

    Aquidneck Guest

    The answer to your question is no, I can't. What I do know is that those two
    applications were installed on client workstations one and three years ago,
    respectively, and have worked perfectly well until KB960715. Nor do I want
    to spend the time to validate what did and didn't get installed with the apps.

    My point is that if MS is going to issue a hotfix that affects VBA runtimes,
    those OCX updates should be included in that hotfix, regardless of whether
    the target machine has them installed or not. They already throw too much
    crud at us, as it is, with automatic updating.

    In my mind, then, you're asking the wrong question. Yes, it's a third party
    app, and regardless of how the OCX files that make it work get there, I think
    the onus is on MS to update affected VBA runtimes at the same time when they
    issue a hotfix that breaks them, regardless of how the broken OCX files got
    installed in the first place.
    Aquidneck, Feb 16, 2009
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.