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-08-09T15:14:57+00:00

    Here’s my two-penneth also, uninstall SP1, as I have done. I’m running 64 bit Windows 7, 32 bit Access. If Microsoft are aware of these issues why are they still distributing it, you would think they would hold it back until they have the fix/ or recommend that those running Access withhold. There that’s better…

    Was this answer helpful?

    0 comments
  2. Anonymous
    2011-08-09T13:38:35+00:00

    I just want to add my 2 cents here too.  I'm using 32-bit Access on Windows 7 and am experiencing the same problems as has been mentioned above by other 32-bit users.  Accdb's crash inconsistently when SP1 installed.  They work just fine after uninstalling SP1.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2011-08-09T09:52:13+00:00

    I am having similar issues. Running 32 bit Office 2010 on W7 64 bit development machine. Having rolled back to pre-SP1 (using System Restore) crashes when editing code seem to have stopped. Compact and Repair also seemed seriously flawed (it managed to halve the size of one accdb file by (probably) deleting a lot of stuff that should have stayed.

    I am also seeing filtering issues as per comment on this post:

    http://blog.nkadesign.com/2011/office-2010-sp1-and-access-2010-runtime-sp1-are-broken/

    but am not yet convinced they are only related to SP1.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2011-08-03T21:33:58+00:00

    Just came across this thread along with a MS KB article that seems related. See:

    Been suffering Access 2010 crashes while attempting to build .MDE's from .MDB (v2002-2003). Have tried importing to a clean/fresh .MDB to limited success.

    I'd been working on the assumption that my dev environment was the cause because I've been trying to run Office 2003/2007/2010 side-by-side; discovered that Access and Word want to do a "mini-re-install?" whenever switching different version. Came across a KB article discussing problems in this environment as being related to running as a non-admin when this switch occurred (running as admin on the swap is suppose to alleviate the issue). Sorry can not recall the specific KB # at this time. NOTE: The swap under a non-admin account would change enough of the environment to run the the different version, but key elements were locked in under the previous version).

    As well didn't really resolve the issue I was seeing vis-a-vis VBE7/VBA problems (running .MDE under Access 2010 runtime complained about corrupt VBE7.dll's).

    My short term solution so far has been to build the .MDE under Access 2003, hopefully having avoided slipping an 2007 or 2010 feature.

    H. Mertens

    Contract & Consulting Services

    Vancouver BC

    Was this answer helpful?

    0 comments