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-10T20:35:34+00:00

    Hi Nathan -

    Just thought I would mention that even though I did a repair on my installation, the problem is continuing to occur.  At one point, I thought I was getting crashes because Access was compacting because almost every time I compacted, I got the error. But this morning I got it AGAIN!  All I did was open the db that I had edited yesterday when it worked fine.  I decompiled it and it worked, but I am concerned that my end-users will see this and it will be a huge issue for us.

    This has gone on for a few weeks now...can you give us any kind of timeframe for resolution?

    Thanks,

    Joy E.

    CDD, Inc.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2011-08-10T17:53:36+00:00

    Hello Everyone,

    As mentioned before, Microsoft is currently looking into the issue and the information everyone has posted has been extremely helpful.  I will definitely post back to this thread when I have any additional information to share.

    Best Regards,

    Nathan O.

    Microsoft Online Community Support

    Was this answer helpful?

    0 comments
  3. Anonymous
    2011-08-10T17:26:56+00:00

    Amazing! I just had my first crash since 7/28. Maybe it was because I read your comment, Jon.

    More wasted time!

    MICROSOFT -- ARE YOU LISTENING???????

    Was this answer helpful?

    0 comments
  4. Anonymous
    2011-08-10T07:35:08+00:00

    Thanks to Darrell for this update. The only slight caution re this approach is from a post by 'SmallTime' in another forum, in which they say:

    'After installing SP1 all my previous ACCDB's seemed ok until I made a change to code, then after compiling, closing and trying to reopen the db's crash. I've also seen numerous other comments with the very same problme. So 32Bit IS an issue.

    What's happened to the guys at MS rolling out a SP without testing it properly. I've wasted days on this.Thought I had it cracked after repairing Office installation but today I'm back with the same problem. If I'd have done this to my customers I'd loose them in flash.'

    [My bold font]

    So it may be that there are specific factors that allow the Repair option to work on some systems but not on others. The core problem remains, and we have still not had an update from Microsoft as to when the full solution will be issued.

    Was this answer helpful?

    0 comments