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: Most helpful
  1. Anonymous
    2012-03-06T00:11:21+00:00

    Nathan,

    First of all, thank you for paying attention throughout this blog. It has proven to be very, very helpful.

    I am attempting to update and repair Access 2003 db to Access 2010. Eventually there will be SQL tables.

    I have had nothing but issues since the update. I love working with 2010 but the crashes have made me look real stupid to my bosses. So far I've had a Just-In-Time debugging error that I finally repaired by removing all files related to Visual Studio. Now I'm having the crash mentioned throughout this blog.... FYI.

    Tonight I'm going to attempt the hot fix. Wish me luck.

    Question... have there been any further updates available that will fix this crash? I've searched and cannot find anything. I just need to know if there is something I need to do beyond this hotfix. I've got an IT guy coming tomorrow and a full team at my disposal when we are ready to upload onto our new network at the factory. I'll need to give them as much instructions as necessary prior to bringing 15 users on line.

    Regards,

    Lynda K.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2011-11-23T14:40:00+00:00

    Hi Heinzi,

    You are correct, you should make a backup copy of the database before using the decompile switch.  With that being said, it was a temporary workaround and now that a fix for the issue is available, I would recommend installing this fix and using it going forward.

    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 O.

    Microsoft Online Community Support

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2011-11-23T08:27:00+00:00

    So I now have shortcuts on my desktop to each of our DB's with the /DECOMPILE switch so when ever I open a DB it is decompiled before i work on it.

    I'm not sure if this is a good idea. Almost every resource on the web talking about the /decompile switch tells you to make a backup copy before. It's an undocumented feature which might not have received production level testing. The following usenet post contains additional information about the background of the /decompile switch: http://www.trigeminal.com/usenet/usenet004.asp

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2011-11-22T15:32:32+00:00

    Hi Nathan,

    Thanks for the reply. I have found the blank form issue gets resolved if you DECOMPILE the DB and then instantly create the ACCDE/ACCCDR.

    So I now have shortcuts on my desktop to each of our DB's with the /DECOMPILE switch so when ever I open a DB it is decompiled before i work on it.

    As for the filtering crashes, I've given up and came at it from a different angle so have rebound the form to the table/query rather than trying to use DAO.recordset and then filtering.

    Now the DB's are back up and running, it's time to move onto web development, no rest for the wicked!

    Was this answer helpful?

    0 comments No comments