none
Critical Bug in Access Database Engine 2010 RRS feed

  • Question

  • Hi,

    Although I don't expect Microsoft take immediate action on this, I just hope they will fix it.

    It's hard for me to explain what happens, just if you are using Microsoft Access Data Connectivity Components 2010 in your application to read data from mdb access files, you might get unexpected exceptions and your application will crash!

    To reproduce this behavior the best way is to run my sample application which will allow you to see the bug directly in no time.

    This behavior may occur at any time, any where, but I found if you use Application.DoEvents, you increase the chance to run your application to crash.

    To reproduce ::

    1. You should not have any Office version installed on your system (I am using Windows 7 x64).

     

    2. Please install the Microsoft Access Database Engine 2010 x86 (or x64 and you'll have to set your project to x64).

    http://www.microsoft.com/downloads/details.aspx?familyid=C06B8369-60DD-4B64-A44B-84B371EDE16D&displaylang=en

     

    3. Download and run my sample application in VB.NT 2010, and press the button, you will get it :(

    http://www.usvpn.org/WindowsApplication1.zip

     

    Where is Microsoft going, do you think?

    Should I hope to receive an official response?

    Tuesday, August 3, 2010 2:51 PM

All replies

  • Can you reproduce this behavior using the Northwind sample database that
    comes with Access?
     
    If not, the problem lies almost assuredly within your own application.
    --
    Arvin Meyer, MCP, MVP
    http://www.datastrat.com
    http://www.accessmvp.com
    http://www.mvps.org/access
    Co-author: "Access 2010 Solutions", published by Wiley
     
     
    "OSVBNET" <=?utf-8?B?T1NWQk5FVA==?=> wrote in message
    news:83574177-e57b-4cac-9d3c-cc3987bfd8c9...
    > Hi,
    >
    > Although I don't expect Microsoft take immediate action on this, I just
    > hope they will fix it.
    >
    > It's hard for me to explain what happens, just if you are using Microsoft
    > Access Data Connectivity Components 2010 in your application to read data
    > from mdb access files, you might get unexpected exceptions and your
    > application will crash!
    >
    > To reproduce this behavior the best way is to run my sample application
    > which will allow you to see the bug directly in no time.
    >
    > This behavior may occur at any time, any where, but I found if you use
    > Application.DoEvents, you increase the chance to run your application to
    > crash.
    >
    > To reproduce ::
    >
    > 1. You should not have any Office version installed on your system (I am
    > using Windows 7 x64).
    >
    >
    >
    > 2. Please install the Microsoft Access Database Engine 2010 x86 (or x64
    > and you'll have to set your project to x64).
    >
    > http://www.microsoft.com/downloads/details.aspx?familyid=C06B8369-60DD-4B64-A44B-84B371EDE16D&displaylang=en
    >
    >
    >
    > 3. Download and run my sample application in VB.NT 2010, and press the
    > button, you will get it :(
    >
    > http://www.usvpn.org/WindowsApplication1.zip
    >
    >
    >
    > Where is Microsoft going, do you think?
    >
    > Should I hope to receive an official response?
    >
     
     
     

    Arvin Meyer MCP, MVP MS-Access
    Tuesday, August 3, 2010 4:41 PM
  • Hello and thank you very much for your response.

    Unfortunately, the problem is not from my application, which is only a few lines!

    It's so easy to re-produce using the sample I have uploaded, the problem is NOT from my application, I have reviewed this issue with many developers in the past 3 weeks before posting here!

    Can you please try to reproduce using my sample? I just need your help so much, just please don't have Office itself installed, specially 2007.

    Tuesday, August 3, 2010 5:13 PM
  • Hi,

    Did you ever get anywhere with this issue. I have exactly the same problem with our product. I did actually report it to Microsoft ages ago during the Office 2010 beta program (or whatever they call it) but nothing ever happened.

    All we can do for our users is advise them to install the 2007 Access driver.

    Cheers

    Rob

     

    Tuesday, September 7, 2010 10:02 PM
  • can you be a little more specific about the error/problem (what are the error messages?)

    (not trying to diagnose anything - just wanting to be able to recognize the issue should it appear again)

    Tuesday, September 7, 2010 10:26 PM
  • The precious time wasted so far.

    After around 1 year of working with Microsoft professional!!! support, they finally found the bug.
    They released a hot-fix for Access Database Engine 2010, without that this driver is almost useless!
    This is the technical details:

    The root cause has somehow to do with the ACE provider but will be caused by a different component owned by office, that is getting loaded by ACE. This DLL (MSO.DLL) is destroying data owned by a thread belonging to a different component. This will later on in the call stack result to the issue you have seen in your application. With this information in mind we could identify an existing HotFix request created by another engineer for a different issue.

    This is the hot-fix they released: KB2516475

    http://support.microsoft.com/kb/2516475

    If you install this hot-fix after installing the Access Database Engine 2010 everything will be OK.

    But what's the problem?

    Microsoft released Access Database Engine 2010 SP1, but didn't include KB2516475!!!
    This means that the driver is still useless!
    It's OK if you embed the Access Database Engine Driver and KB2516475 in your installer.
    But unfortunately, if user already installed Access Database Engine 2010 SP1, KB2516475 WILL NOT INSTALL.
    The same applies to the Office 2010 SP1.

    Conclusion: Microsoft really doesn't want it's developers use this driver in their applications or want to make real problems for them, but why wasted the time? It's really disappointing...
    Friday, July 8, 2011 4:51 PM