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
    2011-09-02T13:26:30+00:00

    Understand, and we have all had this feeling for several weeks now.  What might help slightly to clarify the factors involved in your particular context would be if you could check the version number for your vbe7.dll files on your home computer and at work. It is possible that there is a discrepancy which is causing you additional problems, particularly if you have taken accdb files between machines and then compiled them (e.g. auto compile on close) while they were in the other machine. If you do a file search and then check whether the vbe7.dll version is 7.0.16.19 (after SP1) or 7.0.15.90 (pre SP1)  the discrepancy may have contributed to this additional hassle.

    There is no real solution until MS put out the Fix or an amended SP1, but the additional problem of a discrepancy between home and work systems is one which we are all now having to face.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2011-09-02T13:43:04+00:00

    Hi Jwhite_NC,

    Unfortunately, I don’t think the issue you are experiencing is related to this specific SP1 issue or even the other SP1 issues.  If this is happening for all databases on your machine, including any new databases you create, then you may have something else wrong with your base Access 2010 install (perhaps causes by the side by side Access installs on your machine).  If you have your media and product key for Office 2010, you may want to run the utilities in the article below to completely remove your Office 2007 components and then your Office 2010 components.  I would also have you run the utility to remove the Office 2003 components, but if you only had Access 2003 standalone installed, this may not work, since I believe it only works on suites.  After you run this utility for Office 2007 and Office 2010, I would then recommend installing Office 2010 again.

    290301            How do I uninstall Office 2003, Office 2007 or Office 2010 suites if I cannot uninstall it from Control Panel?

    http://support.microsoft.com/default.aspx?scid=kb;EN-US;290301

    If you still have problems after doing this, I would recommend probably creating a support case with Microsoft, so that we can look at it with you. 

    Online Assisted Support Options (create cases online) - http://support.microsoft.com/select/default.aspx?target=assistance

    Best Regards,

    Nathan O.

    Microsoft Online Community Support

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2011-09-02T22:01:13+00:00

    Thanks Nathan & JonFarmer.  Yes, I did wipe the 2003 and 2007 components with the utilities, including MSO2010, then re-installed MSO2010 before posting here.  I will check the vbe7.dll versions at home/work and report back here.  I did find out today that another person had the same problem as I last year, but didn't report it nor document what resolved it.  They have SP1 installed and are not having any problems at this time -- these would be clean installs on wiped/new drives.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2011-09-04T20:31:01+00:00

    I ran into this problem on Friday.  Adding some information in hope it helps someone:

    My client has a database in 2003 format that I've been developing new features for in Access 2010.  Hadn't done any changes since June -- there were no problems at that time.  On Friday the database crashed repeatedly after I did some changes to the code behind a form.  Repair/compacted multiple times, but sometimes it would crash upon opening, and at other times after I'd been editing forms or code for awhile.  Tried reshelling the FE/ BE (ie copying all objects over to a new database) and was successful moving tables and queries over.  However, any time I would attempt to move forms or reports over it would crash.  Took the DB home and tried opening on Access 2002 -- so far seems to work fine.  I'll try the workarounds listed in this thread next time I'm in the office.

    My error message:

    Faulting application name: MSACCESS.EXE, version: 14.0.6024.1000, time stamp: 0x4d83e4fcFaulting module name: VBE7.DLL, version: 7.0.16.19, time stamp: 0x4d430aecException code: 0xc0000005Fault offset: 0x00023081Faulting process id: 0x14f8Faulting application start time: 0x01cc69c11759b65dFaulting application path: C:\Program Files\Microsoft Office\Office14\MSACCESS.EXEFaulting module path: C:\PROGRA~1\COMMON~1\MICROS~1\VBA\VBA7\VBE7.DLLReport Id: 616b4a1d-d5b4-11e0-ba60-f04da22031a1

    Was this answer helpful?

    0 comments No comments