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-07-22T08:29:36+00:00

    Some have already tried this and it did not work for them. In our case, as with some of the other people who have been having SP1 problems on the forums, this won't work for us  because we have a number of users of various levels of expertise distributed round the UK and we certainly can't expect them to go through decompiling and recompiling existing versions of the system. We cannot at present even send them updates by email because they cannot open them owing to the VBA problem.

    The key point is that Microsoft have put out a Service Pack which is faulty in a really important area; you cannot expect users to have to decompile all their existing databases before they can use them or develop them. We have perhaps 20 different Access 2010 databases dealing with different functions; are we supposed to decompile all of them before we can use them? 

    The SP1 is faulty and it needs fixing urgently; can you please arrange for a notification when the amended update or fix is ready, and we can then try to organise a coherent way out of this mess. It is holding up work and costing us delay money.

    Jon

    Was this answer helpful?

    0 comments
  2. Anonymous
    2011-07-21T21:12:34+00:00

    Hi Jon,

    Did  you try the workaround mentioned above?  After decompiling the application with SP1 installed, it should then work successfully.

    Best Regards,

    Nathan O.

    Microsoft Online Community Support

    Was this answer helpful?

    0 comments
  3. Anonymous
    2011-07-21T19:00:04+00:00

    Just an update to the above reply; when I uninstalled the SP1 update, and the vbe7.dll went back to the previous version, I can now open code pages and the whole accdb functions as normal again. So the bug is specific to SP1. I have switched off automatic updates and will wait until Microsoft confirm that they have issued an amended SP1 or a fix.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2011-07-21T11:40:33+00:00

    Confirm bug in Access 2010 SP1 and it definitely also applies to 32bit running on an XP machine. During my first working session today after installing SP1 (on return from holiday), everything was normal during development of a new form on an existing accdb that had been running for many months, but as soon as I went into VB to add a simple for-next list-clearance code routine behind that form, and then saved/closed the database, Access crashed on closing and has now crashed every time I tried to re-open ANY vb module within the database (not just on the new form).

    So an Access 2010 uncomplicated accdb that has been reliable in development and use for a long time is now inaccessible. This accdb is urgently needed for survey data entry; please put out fix urgently.

    Was this answer helpful?

    0 comments