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-19T18:57:15+00:00

    My experience was creating an empty DB in Access 2010 (no sp1) and importing all objects from Access 2007.

    When we opened Access 2007 DB with Access 2010, it corrupted the Access 2007 database.

    There were many code issues that had to be updated as listed in th Access 2010 SP1 bug fix list. When the October release for the SP1 cumulative patch is available, please release information that an IT network group can understand.

    Too often, the network / server groups will only do what Microsoft clearly describes as necessary.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2011-10-19T18:23:38+00:00

    One further note -

    We noted the same issue as EAB1977 above, specifically when opening a database in Access 2010 that had been created using Access 2007, and experiencing the "Microsoft Access has stopped working" error. Once we opened with the /decompile switch, all the code is deleted.

    You of course get your database, queries, etc.. back, but that code loss is catastrophic in many cases.

    We noted this discovery on site with a client that is required to use a Citrix Xen App server running Access 2007 for many of their queries that utilize remotely hosted server databases, but then copy the ACCDB back down to their local machines running Access 2010 for better speed in accessing local tables.

    We have put a stop to this practice now until the fix is released. But thought it would be helpful to at least corroborate EAB1977's find, and bring it to light for the Microsoft folk as well?

    Was this answer helpful?

    0 comments
  3. Anonymous
    2011-10-19T12:03:53+00:00

    Just a quick heads up - we had this exact same issue with Windows 7 32bit and Office 2010 32bit.

    I just wanted to put this out there as so many of the posts I am reading on this issue specifically reference 64 bit versions, and that is not the case!

    Thanks much for the workaround - we had days of coding into a database this happened with, and the decompile steps referenced above (C:\test.accdb /decompile) fixed it immediately for us!

    Was this answer helpful?

    0 comments
  4. Anonymous
    2011-10-18T23:09:05+00:00

    Hi

    Isnt backup a mantra for any IT pro.

    I have used a routine with development DBs for a few years now that works very nicely . . for me.

    Each day before I start any edits to a frontend, I copy it and date stamp it in the name

    eg DSM_FE.accdb may be the master production version but my development versions would be

    DSM_FE_20111015 . . then the next day . . DSM_FE_20111016. . . and if its been a big session i often do it in the middle of the day and create DSM_FE 20111016A

    And I keep these for several months . . HD space cost nothing . . my time for lost procduction costs a lot.

    Also the development folders are backed up to an alternate PC - taken off server - every 2 hours. - automatically.

    There are lots of causes for lost files . . corruption . . human stupidity etc . . so  to loose more than a days worth of work should never happen. and if done right . . even a few hours should be the maximum.

    lets all have a good day . .

    Cheers

    PaulG

    Was this answer helpful?

    0 comments