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

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

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

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

0 comments

203 additional answers

Anonymous

2014-10-22T17:00:56+00:00

Thats what I'm doing several times a day. I already have a desktop icon named 'DCR' (Decompile / Compact / Repair ) for my libraries.

Changing code in my library (even only adding a comment) will mostly crash the main app. Sometimes the library itself is than so corrupt, that DCR will not help and I have restore it from backup and do the changes again ( so I've lost all my work I've done on monday :-((

Sounds like you better back up every hour! There are lots of freeware backup utilities available.

But I don't get why this is happening anymore than you do. Are you developing locally? If not, could it be a faulty network connection?
Was this answer helpful?

0 comments No comments
Anonymous

2014-10-22T10:29:40+00:00

I have some accdb-Libraries with commonly used code, which I include as reference in my main accdb, and I would bet, that there is a bug in Access regarding those referenced libraries..

Maybe the problem lies in one of your referenced accdb's. Try decompiling and recompiling those.

Thats what I'm doing several times a day. I already have a desktop icon named 'DCR' (Decompile / Compact / Repair ) for my libraries.

Changing code in my library (even only adding a comment) will mostly crash the main app. Sometimes the library itself is than so corrupt, that DCR will not help and I have restore it from backup and do the changes again ( so I've lost all my work I've done on monday :-(( )
Was this answer helpful?

0 comments No comments
Anonymous

2014-10-21T17:32:15+00:00

I have some accdb-Libraries with commonly used code, which I include as reference in my main accdb, and I would bet, that there is a bug in Access regarding those referenced libraries..

Maybe the problem lies in one of your referenced accdb's. Try decompiling and recompiling those.
Was this answer helpful?

0 comments No comments