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
    2012-11-16T13:33:58+00:00

    The button will not add it to the trust center though, you will have to go to Access options, then trust center then trusted locations to add it.  If it is  on a network I am unsure, this is what I had to do to get the frontend where I work at to work.

    Can you believe, that it does work.  Thank you so much.  I thought I would end up having to buy a new disc! :D

    The only problem I have now is the I get the yellow Security Warning bar at the top saying that I have to enable content.  I know this isn't a big thing, but I get people moaning at me that it's a pain.

    Is there any way to get rid of this?

    Was this answer helpful?

    0 comments
  2. Anonymous
    2012-11-16T13:19:21+00:00

    The button will not add it to the trust center though, you will have to go to Access options, then trust center then trusted locations to add it.  If it is  on a network I am unsure, this is what I had to do to get the frontend where I work at to work.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2012-11-16T13:17:10+00:00

    Sounds like your db is not in your trust center.  You should have a yellow bar across the page asking if you trust the db and what to enable scripts.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2012-11-16T12:53:01+00:00

    I work for a small charity.  We recently upgraded one laptop to Microsoft Access 2010, as the 2007 disc had gone missing so we bought a new one.

    My database, which was created in Access 2007 now will not open.  It gets to the database Autoexec page, but when I click on the button to open the database, nothing happens.

    How on earth do I get this sorted???  I have little IT knowledge and we have no IT support.  Surely Microsoft didn't create a package that was not compatible with the previous package? 

    Can someone PLEASE help me... I'm going mad.  And be gentle - as I said, I have little IT knowledge but I'm the best we have!  Thanks. x

    Was this answer helpful?

    0 comments