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: Oldest
  1. Anonymous
    2013-05-29T19:07:28+00:00

    Once in a while, this happens. It can be almost anything that crashes the system.

    This is what is necessary to do every so often:

    1 Make a brand new bland DB, give it a name and save it.

    Use the Access Exteranal Data for Access - use the button to Import Tables, queries, forms, reports, macros an modules into the current Database (the blank one).

    2 Importa all the objects from the previoius (bad) version) Sometimes, the corrupted version will work, sometimes, I have to go back a backup or two.

    1. Be sure to set all fo the Options - Startup form - preferred settings, trust, ...

    This has fixe corrupted objects. It also re-indexes tables. Another advantage is the super compact that it does. In general, it is an important thing to do every so often anyway.

    I notice that the corruption happens when an object, such as a listbox, textbox, that has code behind it is copied. That object can become corrupt. From there, other weird things can cause the Fault or Error. I have had events just stop working. Stepping through the code, the event such as a lost focus, doesn't fire.

    The last time, my project went from over 90 MB to 40 MB. Note, I use linked tables to SQL Server. So, this was not data.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2013-05-31T15:48:35+00:00

    I have a program in Windows 7, Access 2010, that when you go from form view to data view, Access crashes. I cannot uninstall SP1 (even with the tool). I have tried every thing on this thread to no avail. Any ideas?

    Larry

    This sounds like the problem that was caused by SP1 when it first came out. Subsquent updates fixed it. Is your Office 2010 updated to the latest version?

    My 32-bit Access version is 14.0.61.29.5000.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2013-09-12T14:16:41+00:00

    I've had the same problem with crashes.

    The interesting part was that the desktop version did not have any problems, while our server version did.

    Upon checking, the vba7.dll was newer in the desktop version. So I replaced the dll on the server with the newer version and havent had that problem since.

    Jerry

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2013-09-13T14:39:04+00:00

    WEll, that just might be the OP's issue. I know if you install earlier versions of an MS product that uses VBA after you install Office you can end up with the wrong DLL.

    But what surprises me is that you IT department installed Access on a server.

    Was this answer helpful?

    0 comments No comments