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: Newest
  1. Anonymous
    2011-09-08T13:46:47+00:00

    I have Access 2010 on 32 bit Vista with MS Office SP1.

    I tried the decompile today and it worked.

    Thank you.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2011-09-06T20:52:22+00:00

    Hint:  Make sure you enclose the arguments in quotes!!!!!

    "C:\Program Files (x86)\Microsoft Office\Office14\msaccess.exe"  "C:\Users\quimby\Documents\Projects\Acme Corp\Terminal Substation\Transmittals\cm.accdb"   /decompile

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2011-09-04T21:23:00+00:00

    'I ran into this problem on Friday.  Adding some information in hoI take it that the problem only started after installing SP1?

    Uninstall SP1 and wait until it has been fixed.

    It's like Access 2003 SP3 all over again. An inadequately tested piece of code that has critical issues which took weeks to patch. It's been over a month now - come on MS this isn't good enough.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2011-09-04T20:31:01+00:00

    I ran into this problem on Friday.  Adding some information in hope it helps someone:

    My client has a database in 2003 format that I've been developing new features for in Access 2010.  Hadn't done any changes since June -- there were no problems at that time.  On Friday the database crashed repeatedly after I did some changes to the code behind a form.  Repair/compacted multiple times, but sometimes it would crash upon opening, and at other times after I'd been editing forms or code for awhile.  Tried reshelling the FE/ BE (ie copying all objects over to a new database) and was successful moving tables and queries over.  However, any time I would attempt to move forms or reports over it would crash.  Took the DB home and tried opening on Access 2002 -- so far seems to work fine.  I'll try the workarounds listed in this thread next time I'm in the office.

    My error message:

    Faulting application name: MSACCESS.EXE, version: 14.0.6024.1000, time stamp: 0x4d83e4fcFaulting module name: VBE7.DLL, version: 7.0.16.19, time stamp: 0x4d430aecException code: 0xc0000005Fault offset: 0x00023081Faulting process id: 0x14f8Faulting application start time: 0x01cc69c11759b65dFaulting application path: C:\Program Files\Microsoft Office\Office14\MSACCESS.EXEFaulting module path: C:\PROGRA~1\COMMON~1\MICROS~1\VBA\VBA7\VBE7.DLLReport Id: 616b4a1d-d5b4-11e0-ba60-f04da22031a1

    Was this answer helpful?

    0 comments No comments