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: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2011-08-17T19:04:23+00:00

    To the best of my knowledge, you have to include the Access full path before the database file like this (adjust the Access path if yours is different):

    "C:\Program Files\Microsoft Office\Office14\msaccess.exe" /decompile "C:\Users\davidj\Documents\EDI_App.accdb"

    A more convenient way is to create a shortcut for your desktop with this target:

    "C:\Program Files\Microsoft Office\Office14\msaccess.exe" /decompile

    Then you can just drag & drop teh file from the Explorer window.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2011-08-16T17:19:26+00:00

    Hi there

    I simply navigate in the command prompt window to the location/folder where the database is saved.  If the database is called 'example.accdb' I would type in 'example.accdb /decompile' and hit [ENTER].  There is only one space in that command and it is inbetween 'accdb' and the '/'.  The database opens alright for me.  However, yesterday I removed SP1 from my development PCs for the time being to avoid the complications!  Sadly it looks like Microsoft are dragging the heels on this fix.  It is not good PR for them at all.

    Graeme

    Was this answer helpful?

    0 comments
  3. Anonymous
    2011-08-16T16:59:43+00:00

    I am typing in this command from the run window (based on the above syntax) and windows doesn't recongnize it.

    C:\Users\davidj\Documents>/decompile ex. C:\Users\davidj\Documents\EDI_App.accdb  /decompile

    Was this answer helpful?

    0 comments
  4. Anonymous
    2011-08-16T16:58:55+00:00

    I spent several days attempting to 'fix' suspected errors in coding before I came across this thread which indicated the issues were unrelated to my work.  In the past three weeks I have had to decomple or run the fix on Microsoft Office numerous times with varying degrees of success.  Have had to resort to backups when decompile and/or fixes failed at least 15 times.  How long will it take Microsoft to issue a "recall" on their defective product?

    Was this answer helpful?

    0 comments