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-27T09:45:27+00:00

    Think it is worthwhile mentioning another SP1 woe!  I have one machine with side by side Office installations (required becuase i have to work on various DBs of different formats and trying to maintain compatibility whilst working on 2010 with 2003 and even 2K7 is very challenging, often you are not alerted until trying to Save).

    Everything was happy until SP1 was installed and now if i open 2K3 it starts its installer, finishes and opens as normal.

    However, i then open 2k10 it starts its installer, you wait it finishes, opens as normal.  However, go back to 2K3 its installer starts.....get the message!!

    Is there an easy fix for this?

    Mike

    Was this answer helpful?

    0 comments
  2. Anonymous
    2011-07-27T09:28:12+00:00

    Yes, i definitely had this problem and it does seem to be connected with the compilation state.

    I always have 'compile on Demand' turned off and I get the crash if i have made a code change and forgot to check that it compiles correctly before closing the database.  When i reopen it, it crashes on re-opening.

    This suggests it may be mitigated by having 'Compile on Demand' turned on :) but it is always best to see the code compiles before you shut the database.

    Since checking that everything compiles okay before i close it, i have not had the problem.

    Mike

    Was this answer helpful?

    0 comments
  3. Anonymous
    2011-07-25T15:48:36+00:00

    Nathan,

    I did the decompile yesterday and it immediately bounced back. So far so good. I'll keep my eye on it.

    Darrell

    Was this answer helpful?

    0 comments
  4. Anonymous
    2011-07-25T13:33:45+00:00

    Hi Nathan

    Thank you for the workaround which recovers what appeared to be a completely corrupted database.  This has caused me days of angst and extra work at one client in particular.  As a Microsoft Partner developing Access databases as my core business this is a hugely embarrasing flaw in the Microsoft Access Product and I trust the fix will be available soon and delivered via WSUS?

    Many thanks in advance

    Best wishes

    Graeme Whyte

    Was this answer helpful?

    0 comments