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: Most helpful
  1. Anonymous
    2011-08-16T16:10:21+00:00

    I too am suffering continual problems with my ACC2010 VBA crashing out and corrupting databases. Thought it was me till I found this thread. Productivity has been down the pan recently. Hope a proper fix very soon. - not sure how long current situation is sustainable!!

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2011-08-16T09:58:06+00:00

    I just had another crash but this time neither repairing Office nor decompiling fixed the problem.

    Just want to keep this issue on the front burner..

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2011-08-13T19:36:09+00:00

    Nathan,

    Thanks for letting us know that people are still working on the fix, and agree that many people will have already uninstalled SP1 until the issue has been resolved. The problem is that most of our clients are set to automatic updates, so they now already have SP1 installed. We can't tell them to uninstall SP1, since their levels of expertise vary and we don't want to risk interfering with other Office or other application software.

    So although we can develop code on our own systems with SP1 uninstalled, we cannot risk distributing any updated components to clients with SP1 still installed. As a result, all Access database development distribution is effectively frozen until you roll out the fix.

    Please do ensure that the people working on this are fully aware of the implications of what has happened, and we are grateful for your assurance that you will post when the fix is available.

    Regards

    Jon

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2011-08-10T20:51:07+00:00

    Hi Joy,

    Unfortunately, I don’t have a timeframe as to when a fix will be available.  But I will definitely post here when I have additional information to provide.  As far as decompiling the database, this seems to work until certain VBA changes are made to the database again.  Once these changes are made, if it crashes again you may have to run the /decompile again.  If you are doing a lot of development work in your database, then it may be beneficial for you to temporarily uninstall SP1 until the issue has been resolved.

    Best Regards,

    Nathan O.

    Microsoft Online Community Support

    Was this answer helpful?

    0 comments No comments