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
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

203 additional answers

Sort by: Newest
Most helpful Newest Oldest
  1. Anonymous
    2011-07-28T17:43:54+00:00

    You are probably careful to avoid doing this, but all versions of Access have a fairly good chance of corrupting the code project if a form/report's code is edited in any way without going to design view first.

    If you are editing a form's code with the form in form view, then it looks like SP1 raised the chance of corruption to 100%.

    No, I wasn't aware of that. But I never had this problem in earlier versions.

    What do you mean by " it looks like SP1 raised the chance of corruption to 100%."

    Was this answer helpful?

    0 comments
  2. Anonymous
    2011-07-28T16:58:57+00:00

    You are probably careful to avoid doing this, but all versions of Access have a fairly good chance of corrupting the code project if a form/report's code is edited in any way without going to design view first.

    If you are editing a form's code with the form in form view, then it looks like SP1 raised the chance of corruption to 100%.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2011-07-27T16:24:06+00:00

    Strongly agree Darrell, and thanks for this very helpful update, particularly the confirmation that the decompile workaround is not a permanent or a realistic solution in a client context.

    Since uninstalling SP1 here, everything has been functioning normally across all apps. We can only hope that Microsoft is monitoring this real-world experience with SP1 and is urgently working on a revised SP1 (or at least a reliable fix).

    Was this answer helpful?

    0 comments
  4. Anonymous
    2011-07-27T14:13:18+00:00

    I spoke too soon. After making some code changes and shutting down at the end of the day, the next time I went to start up I got the same error. BTW, I always compile before exiting. So, running decompile from the command line works temporarily, but this is clearly not an acceptable solution for my clients.

    I've also gotten 2 other crashes in non-Access apps in the last couple days. One was Symantec Whitelist and the other Outlook. Strange coincidence?

    At this point I think my only alternative is to uninstall the Office 2010 SP1.

    The time I've wasted on this is killing my productivity!

    Was this answer helpful?

    0 comments