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: Oldest
  1. Anonymous
    2011-10-17T18:37:50+00:00

    To Everyone,

    As far as the fix itself goes, I do apologize for the inconvenienced it has caused, I completely understand how this is affecting each of you.  Unfortunately, I don’t have anything to do with the fix itself, and am kind of just the messenger at this point.  Thought it has been a few months to get a fix out, I would assume one reason for that is because the fix most likely will affect all Office products and like any other fix it will need to once again be tested.  I say this because based upon the crash log, it looks like the VBE7.dll file is crashing and this file is used by many of the Office applications.  Since there is a chance that it affects multiple Office products, the fix most likely needs to be tested in all sorts of different scenarios / products to ensure other functionality is not broken and that can take some time (just my assumption).  I can assure you this issue is being looked into and I will definitely post back to this thread when the October Cumulative update is released.  Once again I apologize and thank you for your patience.

    Best Regards,

    Nathan O.

    Microsoft Online Community Support

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2011-10-17T22:39:49+00:00

    Nathan,

    Thanks for keeping up with the posts, I understand that you know very little about what's going on at MS and so can't give any definitive answers, I suppose you're in the same boat as us.

    Here's a suggestion, how about getting someone who does know what efforts are being made to answer some of the many questions being asked here.

    Many thanks

    SmallTime

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2011-10-18T14:37:24+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

    Nathan - I tried the workaround and it completely blew away all of my VBA code. Why isn't this in the article? I am extremely pissed right now because it took almost a year to develop and impliment my code and now, I can't even get to the backed up code!

    GET THIS FIX DONE ASAP!

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2011-10-18T15:01:30+00:00

    Hi EAB1977,

    What do you mean it “blew away all of my VBA code”?  Do you mean the code was deleted or you receive errors when trying to view the code?  I am assuming you made a copy / backup of your database before going through the steps.  If so, that copy wouldn’t have been affected by these steps.  So my recommendation would be to once again make a copy of that backed up database and then uninstall SP1 from your machine until the fix is available.  You should be able to uninstall SP1 by going into the Add / Remove program list and find it within the installed updates list.  If you still have a problem after you uninstall SP1 then there is a good chance that your file may actually have been corrupt and may not be related to this issue.

    Best Regards,

    Nathan O.

    Microsoft Online Community Support

    Was this answer helpful?

    0 comments No comments