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
    2014-10-21T14:57:13+00:00

    And I wonder if anyone at MS ever does anything with those error reports.

    Me too ;-)

     I have sent over 500 error reports on my old machine with Access 2007.  ( a lot of them with vbe6.dll )

    Desperately I  moved to a new system with Access 2010, and now have almost 500 error error reports too.

    I have the same errors on my notebook and on a virtual machine too, so I don't think it's specific to the Access installation on my machine.

    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..

    Was this answer helpful?

    0 comments
  2. Anonymous
    2014-10-20T18:47:01+00:00

    Klaus

    This really shouldn't be happening anymore. It sounds more like your Access installation is causing it. Try either running the Office Repair or uninstall Access and then re-install it and run the Office Update to get the latest patches again.

    And I wonder if anyone at MS ever does anything with those error reports.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2014-10-20T15:31:23+00:00

    Anything I can do with this problem?

    I still have crashes with Access2010 SP2 !!!!

    Opening the database, go into VBA Editor, compile the code and close the database, and Access will crash !!

    I tried everything I found in the web: Decompile/Compact/Repair, export everthing in Textfiles and reimport them in a new database.

    I have send over 500 !!!! error reports to MS in the last 6 Months, but despite several patches the problem ist still there.

    Name der fehlerhaften Anwendung: MSACCESS.EXE, Version: 14.0.7104.5000, Zeitstempel: 0x51ce12f7

    Name des fehlerhaften Moduls: VBE7.DLL, Version: 7.0.16.28, Zeitstempel: 0x506f83c8

    Ausnahmecode: 0xc0000005

    Fehleroffset: 0x000642c5

    ID des fehlerhaften Prozesses: 0x167c

    Startzeit der fehlerhaften Anwendung: 0x01cfec771c71e19d

    Pfad der fehlerhaften Anwendung: C:\Program Files (x86)\Microsoft Office\Office14\MSACCESS.EXE

    Pfad des fehlerhaften Moduls: C:\PROGRA~2\COMMON~1\MICROS~1\VBA\VBA7\VBE7.DLL

    Berichtskennung: 613a2001-586a-11e4-bc68-0026832d9af8

    Klaus

    Was this answer helpful?

    0 comments
  4. Anonymous
    2013-09-13T16:38:26+00:00

    Please explain the surprise of installing Access on a Server?

    We deploy Access on a Citrix server to hundreds of concurrent customers nationally on many different client platforms (including Apple).

    To do that, Access must run on the application server.

    The Access Web version is way to limited to be an option here.

    Regarding the VBa7.dll and all of the other aspects of developing on a desktop and deploying off of a server, it is very important to keep things consistent.

    Granted, Access might be a VM on a server, but just wondering why the surprise?

    Regards:

    We run a SQL Server back-end with Access clients running on Citrix.

    We securely deploy many different Access 2010 applications over extremely low bandwidth.

    All Access reports are completed using Excel Object Model Programming with VBA (we don't use the Access Report objects).

    Was this answer helpful?

    0 comments