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

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 No comments
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 No comments
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 No comments
Anonymous

2011-07-28T21:47:26+00:00

Whether you did or didn't, it's a good habit to go to design view before editing a form/reports code.

Since others have said the problem occurs even when they are careful about only editing code in design view, the SP1 problem seems to be independent of the design view issue, even if the corruption symptom is similar enough to confuse two different problems.

Regardless of the design view issue, I find it difficult to imagine how such a gross failure can get past the test team and into the release of a full service pack.
Was this answer helpful?

0 comments No comments