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-11-09T09:23:41+00:00

    Saar,

    Following your post a few moments ago I opened a database which I had been working on yesterday without any problems. It had been modifying and operating normally after installing the fix.

    This morning, when I attempted to use a button within the main opening page to open a form that I had been working on yesterday, I got ....................... Yes, you were right. I got a Return without Gosub error.

    The only thing which has changed since yesterday is that yesterday evening after finishing work on that database I went to Microsoft Update and downloaded and installed the current batch of monthly Microsoft Updates. These included a group of Office 2010 updates.

    Aaagh ........... it looks as though the team working on the fix had perhaps not integrated their work with that of the team working on the other Office 2010 updates.

    So you are right ........... something is STILL not fixed.  This is getting beyond reasonable. Nathan, please get onto this urgently.

    ADDENDUM in case it helps: Having done some further work to narrow down the point where the Return without Gosub error was occurring, the button concerned used an embedded macro to open the required form. When I replaced this embedded macro with a standard VB instruction to open the form, the error did not occur. I'll keep testing.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2011-11-09T07:28:58+00:00

    Hi!

    I installed the fix when it came out and it worked wonderfully! Until yesterday.

    I made several changes to my database, deleted some buttons and created others. The buttons use macros. When we used the buttons, it gave us a Return without GoSub error. On closing the error message, the macro then gave error number 2950. This basically says that the database is not a trusted source. Which is not true.

    This made me think of all the previous not trusted error messages that I received. I then decided to decompile the database. It worked.

    Something is still not fixed.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2011-11-05T03:18:25+00:00

    If you read through the last couple pages of this thread, you'll see that this issue has already been discussed -- and that there already is indeed a 32-bit version available for download.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2011-11-05T01:32:43+00:00

    What's your intent here Nathan? Just to **** us off? Or are you Office monkeys really as pathetic as you appear to be?

    The link you supply will only allow me to download the 64-bit version of the patch.

    Well, guess what, I and everybody else I know who is forced to use this third world product use the 32-bit version.

    I suppose that will be released at the end of November?

    Was this answer helpful?

    0 comments