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-29T13:42:03+00:00

    Same/similar issues here. Switched from OffXP to 2010 beginning of year and converted DB to Access 2007 DB. Waited until 2010 to upgrade and very dissatisfied - quite surprised how unreliable the platform is - Access 2010 has been very unstable and buggy from the beginning.

    After SP1 DB crashed and I lost my entire VB project (8 years of code).

    Rolled back Friday to pre SP1 - hoping to build new database that is stable.

    MS please seriously look into the Access 2010 platform and bring it up to the standards we relied upon in previous versions.

    Win7 64bit

    Office 2010 Pro 32bit

    Was this answer helpful?

    0 comments
  2. Anonymous
    2011-08-27T13:12:31+00:00

    I can confirm this bug also.

    The company I work for just upgraded to 2010,  I have the same problem, same service pack, same vbe version.  I find the issue arises when you log off or restart the computer.  I can open and close the db as many times I need in one session but as soon as I log off and back on then if I try to open the visual basic editor it shuts down Access.  I have also found that if the db Default Open Mode is set to shared, it maintains the laccdb file but not if set to exclusive when you use the application.quit call (same with the docmd.quit).  If you close Access with the close button (upper right corner) it does not maintain the laccdb.   I am in the process of updating our db from Access to 2k to 2010.  No other users, just me designing.  It happens to any db not just the one I am working on.  Trust me, I have started over many times from scratch.  The suggested work around I found on my own but I do not agree that it is a solution.  Decompile can cause issues as well so always copy your db before doing so.  No very satified with this version.  Every version has bugs but this should not happen with a service pack. 

    Access 2010 SP1

    Windows XP sp3 32bit

    vbe7.dll ver.7.0.16.19

    Was this answer helpful?

    0 comments
  3. Anonymous
    2011-08-24T14:20:00+00:00

    Nathan,

    Thank you for the update.  I'd rather hear that it is still being looked into than not hearing any updates at all.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2011-08-24T13:48:55+00:00

    Hi Jon,

    Unfortunately, I don’t have any new information to share at this time other than the issue is still being looked into.  Once I am given any more info, I will definitely pass it along. 

    From an Access Support perspective, the best workarounds I have been giving to customers are to:

    A.       Use the decompile switch to temporarily workaround the problem.  As mentioned several times on this thread, this is just a temporary workaround and does not permanently fix the issue.

    B.      If the databases you and/ or your customers are using are affected by this and the first option doesn’t work for you, then you could temporarily uninstall SP1 from your machine until the issue has been resolved.

    Best Regards,

    Nathan O.

    Microsoft Online Community Support

    Was this answer helpful?

    0 comments