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
    2012-11-22T15:47:34+00:00

    Many thanks for this, Nathan.  Workaround worked, and I could proceed with my work.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2012-11-16T21:17:32+00:00

    Nathan, or anybody,

    Yes, 2012 and here I with this exact problem.  Sadly my anger and frustration appears to have the best of me for I cannot seem to make this work.  I bought/loaded 2010 in May (I'm an old 2000 and before user) AND was on forums, chat, then 10 calls to CS who could NEVER get em to Tech support, who then want to give me support options although I have a year.  Finally, I found this....but cannot get it right.

    1.  I tried the decompile, got hieroglyphics so I figured it worked, but no.

    2.  Then I downloaded and ran the hotfix, with some glitches, but that did not work.

    I think I need a little more specific help on the run command or?  Is access supposed to be open or closed?  It says to make a back-up (obviously) then run the decompile, then close the database.  Close?  That is not very clear.  Help please?  Very frustrated.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2012-11-16T16:36:50+00:00

    I did not have to enable once the location is setup in the trust center for the db.  I have front end deployed on multiple computers in our factory with the backend on the network.  I only had each user add the path to the mde or accde folder for the front end in the trust center settings, trusted locations and the popup ribbon went away.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2012-11-16T15:37:02+00:00

    You will have to adjust your Macro Settings.

    Go to File, Options. Trust Center, Trust Center Settings.

    Click on Macro Settings and select a less secure setting. If it's all internal, select the last option "Enable all macros..."

    Good luck!

    Was this answer helpful?

    0 comments No comments