Access 2010 SP1 – You receive random crashes in certain database or when opening the VBA window in those databases after installing Office 2010 SP1

Anonymous
2011-07-20T15:29:21+00:00

Issue:

After installing Office 2010 SP1, you may receive random crashes when opening objects in certain databases and when trying to open the VBA window in those databases.  If you look in the event viewer the crash info may look similar to the following:

Faulting application: msaccess.exe

Version: 14.0.6024.1000

Stamp: 4d83e4fc

faulting module: vbe7.dll

version: 7.0.16.19

stamp: 4d430aec

Workaround:

UPDATE: Microsoft is aware of the issue and has scheduled a fix to the VBE7.dll in the October 2011 Cumulative Update.  You can workaround the issue by performing the following steps to decompile and recompile the database.

1.      Make a copy / backup of your database.

2.      On the problematic machine decompile the database by running the following from a Run command line:  <path to database file> /decompile ex. C:\test.accdb  /decompile

3.      Close the database.

4.      Open the database again normally.

In addition to this, if you experience the crash please send the error report when prompted to do so after the crash.

2625046 Access 2010 crashes in VBE7.DLL after installing Office 2010 SP1

http://support.microsoft.com/default.aspx?scid=kb;EN-US;2625046

Best Regards,

Nathan Ost

Microsoft Online Community Support

Microsoft 365 and Office | Access | For home | Windows

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments
Answer accepted by question author
Anonymous
2011-10-29T04:36:47+00:00

Hey Everyone,

It looks like the hotfix for this issue has been released and can be downloaded from the link below:

Description of the Access 2010 hotfix package (Vbe7-x-none.msp): October 25, 2011 - http://support.microsoft.com/kb/2596585

In addition to this, KB 2625046 which describes this issue will also be updated to point to the fix above.

Best Regards,

Nathan Ost

Microsoft Online Community Support

Was this answer helpful?

4 people found this answer helpful.
0 comments No comments

203 additional answers

Sort by: Newest
  1. Anonymous
    2011-11-02T15:28:04+00:00

    Nathan,

    1. Go to the Hotfix KB page: http://support.microsoft.com/kb/2596585
    2. Click on "View and request hotfix downloads" in the upper left-hand corner.
    3. In the list of hotfixes, you see the following table:

    Select | Product | Language | Platform | Release | Fix name

    [ ] | Microsoft Access 2010 | All (Global) | x64 | sp2 | office2010kb2596585fullfilex64glb

    ==> In the "Release" column, "sp2" is shown. I guess this is what Jon is referring to.

    Best regards,

        Heinzi

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2011-11-02T15:19:44+00:00

    I installed the Hotfix on Monday morning and have been working on the same database all week now without any issues.  This is the same database that was crashing previously.

    So far in my case the Hotfix appears to be working.

    Nathan,

    Thank you for keeping us updated and you deserve some credit for being a middle man in this mess.  I hope the team behind you takes the time to read through these 15 pages, after that I'd expect them to buy you lunch and bring you coffee for a week.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2011-11-02T15:14:10+00:00

    Hi Mike,

    Sorry for not responding sooner.  I personally haven’t had a chance to apply the hotfix against a runtime build, but I would assume it should apply to that as well since they normally apply to both the full and run-time versions of Access. 

    Unfortunately, I don’t have any information as far as a timeline for if or when SP2 will be released.  So my recommendation would probably be to ensure your users install this cumulative fix after your application is installed.  You may be able to chain this to the installation of your application.  You would just want to ensure, you install the proper bit version of the fix to match the Access 2010 bit version you installed.

    Best Regards,

    Nathan O.

    Microsoft Online Community Support

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2011-11-02T15:08:49+00:00

    Jon,

    I am not seeing where it says, “release SP2”?  If possible, could you guide me to where you see this listed?  This fix is not considered SP2, but is a cumulative update.  Normally cumulative updates are then a part of the next service pack whenever it is released.  Which would mean if a user hasn’t installed the cumulative update, they most likely would receive it when the next service pack is released and installed.

    As mentioned in the “Prerequisites” section of the article, it states you have to have Microsoft Office 2010 installed (if it depends upon another service pack or update it would list it here).  The fix doesn’t depend upon having SP1 installed or any other fixes installed.  Also as mentioned in the “Hotfix Replacement Information”, it states this hotfix doesn’t replace a previously released hotfix.

    So to summarize, this fix is not SP2 nor does it replace SP1.  I would normally recommend installing updates in the order they were released, which would mean installing SP1 and then the cumulative fix.  But since this fix doesn’t depend upon SP1 being installed, you can install it without having SP1 installed and when you do install SP1; it shouldn’t replace the newer version of the files listed in this article.

    As mentioned by others, when downloading the fix, you will want to make sure you download the hotfix that matches the bit version of Office you have installed.  I believe the hotfix site currently looks at the OS bit (64 or 32) and by default shows the hotfix for that build.  If you have 32 bit Office / Access 2010 installed on a 64 bit OS, you will want to make sure you download the 32 bit (x86) hotfix.

    Best Regards,

    Nathan O.

    Microsoft Online Community Support

    Was this answer helpful?

    0 comments No comments