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-10-27T21:37:35+00:00

    October 2011 is now passed for all practical purposes. Will Microsoft announce a new deadline? Or will the patch just be part of Microsoft Office 2012?

    To answer the question has anything been fixed in SP1: There is a huge list of "fixes" in Office 2010 SP1. They are really needed.

    Example: For Office Automation the CopyFromRecordset and other SQL functionality truncates Access Memo fields at 255 characters when moving to Excel. Those of us who use Excel Object Model code to create BI reports from Access applications must come up with alternative custom functionality to meet customer request and deadlines.

    What does it say about a company when a classic flagship product has issues and is no longer a priority to correct?

    B.T.W. There is no such thing as Office 2012. - it is just fustrating that Office 2010 is evidently not going to be working in 2011 at this rate.

    Can I ask why the **** we are paying such large amounts of money to MS for the privilege of using Access? I have NEVER used pirated copies of their programs before, but having just purchased in the past month 11 computers with Windows 7 64 bit and Office 2010 Pro I think that this latest fiasco means that I have paid money to Microsoft for the final time. One very pi**ed of developer.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2011-10-27T15:00:11+00:00

    October 2011 is now passed for all practical purposes. Will Microsoft announce a new deadline? Or will the patch just be part of Microsoft Office 2012?

    To answer the question has anything been fixed in SP1:  There is a huge list of "fixes" in Office 2010 SP1.  They are really needed.

    Example: For Office Automation the CopyFromRecordset and other SQL functionality truncates Access Memo fields at 255 characters when moving to Excel. Those of us who use Excel Object Model code to create BI reports from Access applications must come up with alternative custom functionality to meet customer request and deadlines.

    What does it say about a company when a classic flagship product has issues and is no longer a priority to correct?

    B.T.W. There is no such thing as Office 2012. - it is just fustrating that Office 2010 is evidently not going to be working in 2011 at this rate.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2011-10-26T22:36:29+00:00

    Regular backup is definitely the key here!

    I don't know what on earth has gone wrong but after coping fairly successfully with the decompile workaround, I've had to make a backup after every single change in code since yesterday. So, I make a change in code. Close the database. Save a copy. Decompile the original and then make the next change in code. This was after it crashed about five times or so.

    It works. But it is ever so frustrating!

    Was this answer helpful?

    0 comments
  4. Anonymous
    2011-10-26T22:29:44+00:00

    hi .

    My dev PC just did an automatic update and installed SP1.

    MAS2010 runs very slow in design mode . . clicking on subforms to make a change took a minute before the update and still does . .

    So far - touch wood - i have not had a "crash"

    But I am doing very regular backups

    Has anything been "fixed" in the latest SP1 ?

    fingers crossed . .

    PaulG

    Was this answer helpful?

    0 comments