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: Newest
  1. Anonymous
    2011-11-09T16:16:04+00:00

    Nathan,

    Understand re the function of the Hotfix.  The point was that

    1. the embedded macro behind the main form button was a simple instruction to open another specified form.
    2. I had never had any error with that simple embedded macro either before OR after installing the fix. After installing the fix, I had been working on that database yesterday (including routine use of the button concerned) and had not had any problems developing or using it.
    3. After installing the last batch of Office 2010 updates last night, I then did have the Return without Gosub error immediately today, when I opened the database and clicked on that main form button as I had done countless times before
    4. Removing the embedded macro and replacing it with a VB instruction to open the form removed the Return without Gosub error

    Logically, the problem may associated with one of the 2 or 3 Office 2010 updates I noticed were included in this last patch Tuesday batch. This is clearly something which needs to be brought to the attention of the teams concerned, since 2 developers have so far had the same error. No doubt others will follow.

    We are not really interested in whether it was the fix or the other Office 2010 updates or some lack of integration between them. Rather than creating different threads, all we request is that you bring this to the notice of the teams concerned so that they can jointly look at any interactions between the fix and these last updates in respect of embedded macros.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2011-11-09T15:34:51+00:00

    Hi Paula,

    I would definitely move forward with installing the fix, especially if you already have SP1 installed.  I’m not sure what other issues you have seen reported after installing the fix, but from what I can see it has worked for the majority of the users that installed and it should resolve your crashing issue.

    Best Regards,

    Nathan O.

    Microsoft Online Community Support

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2011-11-09T15:15:14+00:00

    I have not tried the hotfix due to all the issues reported here.  I cannot chance it that my Users will have other issues.

    I have decompiled access.exe, and followed the instructions to recompile each database app that I develop ... and IT HAS WORKED temporarily - like for a day.  But I am delighted that I can at least develop for 8 hours with no issues, and go through the decompile process again when needed.

    I've followed Roger's instructions here ... and it works!

    http://rogersaccessblog.blogspot.com/2009/04/how-do-i-decompile-database.html

    Paula

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2011-11-09T15:02:12+00:00

    JonFarmer, I'm not sure if this will help you but you might make sure all your references are up to date.  This morning, I installed a modification to an adp on a customer's machine which has been running like a champ for nearly ten years.  The adp blew up on me with weird automation errors.  I checked the references and noticed there was an upgrade for reference "Microsoft Activex Data Objects 2.5 Library".  It's up to 2.8 now.  After I installed that, the adp works like new again.

    Saar, I get the Return without GoSub error occasionally, even before the SP1 issue.  For some reason, a recompile seems to take care of it.  I sometimes get it after making extensive modifications to the code.  And to make things really weird, I don't believe the error happens on the event I modified.

    I'm not having any more issues with SP1 since the hotfix.

    Was this answer helpful?

    0 comments No comments