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-07-28T20:20:02+00:00

    Darrell, the usual Control Panel/Add Remove was what I used but you have to tick the 'Show Updates' marker to see SP1.  Good luck and thanks so much for your posts throughout; which have been much appreciated

    Was this answer helpful?

    0 comments
  2. Anonymous
    2011-07-28T20:05:03+00:00

    Jon, how do you uninstall SP1? I don't see an entry for it in the Program list.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2011-07-28T18:37:57+00:00

    You said that every code change caused you to do a decompile the next time you open the db so it sounds like it always corrupts (i.e. 100%).  In my experience, editing code in form view corrupted the code project about 20% of the time (seemed to go up with the amount of code).  So, if you are not going to design view before editing code, the odds went up from about 20% to 100%.

    If you always go to design view before editing code, then you are seeing a new problem.

    Sorry if I wasn't clear, but I didn't say that EVERY code change forced a decompile. Maybe it happened only when I didn't drop into Design View first, but I wasn't looking for that condition. I will now.

    • DB

    Was this answer helpful?

    0 comments
  4. Anonymous
    2011-07-28T18:31:03+00:00

    OK: This one has me spooked, especially after I couldn't even get back into Access before (finally) figuring out that I could bypass the the crash by double clicking on another database in explorer.

    Then again: Maybe not a bad thing... found out that FileMaker Pro apps are available for ipods 'n pads ...

    Back to the point:

    MS never sent out a warning about this problem and I'd be surprised if they're planning to let everyone know that there is a fix ... so what's a good way to keep track of this (other than this thread), presuming that MS is actually going to do something about it.

    BTW: More frequent (hourly) backups and decompiles and elimination of SP1 appear to be working, for the moment, so I am able to bring some old backup copies up to date and, fortunately, I've kept data in separate databases. Data has not been affected yet. However, this is a busy season for the business and I'm stuck recovering functionality and learning a different database program ... just in case ....

    Was this answer helpful?

    0 comments