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
    2011-10-18T16:39:50+00:00

    EAB1977 and JD,

    I don't want to add insult to injury, but I don't see how you can lose several years of backups of your code due to even the most damaging bug or even a virus. While this doesn't excuse a serious bug such as the one in discussion, failure to make backups (even off-site) is even less acceptable for any serious developer. Furthermore, to place blame elsewhere is even more amateur.

    Sorry to disagree.

    Mike

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2011-10-18T16:30:57+00:00

    As a result of this issue I have changed my backup strategy.  I used to back up my work once a week.  Now I back it up every-time I make changes or daily if I'm working on a new project.

    Before I found this decompile work around I was saved by a 3 day old back up!

    It cost me an extra few minutes a here in there, but it is better than starting from scratch.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2011-10-18T16:25:04+00:00

    EAB1977 - I lost SEVERAL years of code after installing SP1 - I DO feel your pain!  AFTER rolling back to Pre SP1 and a few repairs I totally rebuilt my access app.  Was able to import the backed up VBA modules but had to rebuild most of my forms because their Microsoft Access Class Objects were corrupted...

    Good Luck!

    JD

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2011-10-18T15:21:44+00:00

    Thank you everyone for posting your experience. We had the IT dept spring Office 2010 on us a couple of weeks ago. So lucky they did not apply SP1. I have been coding around all the issues this created.

    I have been programming since Access 1.x and this issue appears to be the biggest problem to date.

    Microsoft Access on Terminal Server has been a huge resource for international companies that would not consider cloud or .Net applications for small decision making groups of 10 to 40 people.

    There is great excitement that Access 2010 might integrate with Share Point. The Small Business in the US really depend on Microsoft to provide working products. Once this issue is resolved, my prediction is that Share Point sales will increase. I hope MS marketing understands this relationship.

    The patch this October is huge news. Please include language to IT support staff to guide them of its critical nature.

    Was this answer helpful?

    0 comments No comments