We are experencing the same problem as described here in a post on Microsoft Answers.  However was are also still occasionally seeing the problem after uninstalling SP1. 

Has anyone come across any better workarounds? 

Microsoft: can we please have some information on when this is likey to be fixed - this is a major problem!

--------------------------------------

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:

Microsoft is aware of the issue and it is currently being investigated.  In order to work around the problem, you can try the following:

 

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: MSACCESS.EXE <path to database file> /decompile

(example: C:\Program Files (x86)\Microsoft Office\Office14\MSAccess.exe "C:\folder\database.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.

--------------------------------------

 

Hello,

Have you tried the workaround? It should work after you decompile your databases.

And if there is better solution released by Microsoft, you will be able to find them in certain KB like:

http://support.microsoft.com/kb/2533794

Sincerely,

Max Meng
Forum Support
Please remember to mark the replies as answers if they help and unmark them if they provide no help.
If you have any feedback on our support, please contact tnmff@microsoft.com.

Hello?

Hi Max,

Sorry for the delay, I've been out the office for a few days.

Yes, the work around works - in as much as you can get the database working again.. but it keeps happening.  Basically you can't develop in Access 2010 SP1 - its does it even with a new database created in Access 2010 SP1

There is obviously a major bug introduced by SP1

Are you aware of any patches being worked on?

 

Regards,

Daniel

Hello Daniel,

Unfortunately, we don't have any information to report other than what was provided by Nathan on the Answers site. Our development team is aware of the impact this is having and consider fixing it a very high priority. They are working on fixing the problem but unfortunately, we don't have an ETA at this time. We will update the information on the Answers site as soon as we have any further information.

Just to add, since installing SP1 I am having the exact same problems.

After each crash, I do the decompile/recompile routine and then it runs fine until I start editing forms/code etc and then we are back to crashing again constantly.

I am submitting several crash reports per day now, hopefully this gets resolved ASAP.

Just wanted to add in that I am also having the exact same problem.  This is very frustrating, but I am SUPER happy I found this thread because the decompile method did in fact make my db work again.  I am just about done developing this particular database and I am now leery of distributing it to users for fear this will just happen over and over again.

 

 

Here is crash info from event viewer:

 

 

Faulting application name: MSACCESS.EXE, version: 14.0.6024.1000, time stamp: 0x4d83e4fc

Faulting module name: VBE7.DLL, version: 7.0.16.19, time stamp: 0x4d430aec

Exception code: 0xc0000005

Fault offset: 0x00023081

Faulting process id: 0x764

Faulting application start time: 0x01cc5dced6dbc9ea

Faulting application path: C:\Program Files (x86)\Microsoft Office\Office14\MSACCESS.EXE

Faulting module path: C:\PROGRA~2\COMMON~1\MICROS~1\VBA\VBA7\VBE7.DLL

Report Id: 17daeaca-c9c2-11e0-b526-005056c00008

 

 

SP1 Now UNINSTALLED - Please test SP1 with databases in the future

 

DWV-Access,

From my experience, if you decompile/recompile and do not make any edits in VB or change any design aspects of forms/reports etc. it will remain stable.

I removed the SP1 patch this AM and it has not crashed since. Here is the crash info from my recent crashes, they are all the same for me and the same as posted above by others

Event Type:    Error
Event Source:    Microsoft Office 14
Event Category:    None
Event ID:    1000
Date:        8/17/2011
Time:        5:26:40 PM
User:        N/A
Computer:    LAX-ANDREU
Description:
Faulting application msaccess.exe, version 14.0.6024.1000, stamp 4d83e4fc, faulting module vbe7.dll, version 7.0.16.19, stamp 4d430aec, debug? 0, fault address 0x00025d94.

try hotfix http://support.microsoft.com/kb/2596585

I can confirm that the hotfix works a treat! Before it was applied corrupted databases were failing to open, crashing each time I attempted to open a module, after hotfix no problem. Did not require a de-compile (or a re-boot!)

Pheewwww & thanks dabma_

Can anyone state what "real" benefit you got from doing the SP1 upgrade on Access 2010 ? There are many bugs but SP1 did not last long for me so I never could see any benefit from it.

Not sure whether a patch to fix a patch is worth the effort. Also, does anyone know if the SP1 upgrade now includes the hotfix ?

Thanks

I was hoping someone could help me with a RAMDOM (meaning it occurs with some but not all client machine) error we get from access application on windows 7 + Office 2010 + SP1 + KB2625046 + KB2553385.

Faulting application name: MSACCESS.EXE, version: 14.0.4750.1000, time stamp: 0x4b8bade7

Faulting module name: VBE7.DLL, version: 7.0.16.25, time stamp: 0x4e49ae34

Exception code: 0xc0000005

Fault offset: 0x00004b32

Faulting process id: 0xd88 Faulting application start time: 0x01cd0e4460cef399

Faulting application path: C:\Program Files\Microsoft Office\Office14\MSACCESS.EXE

Faulting module path: C:\PROGRA~1\COMMON~1\MICROS~1\VBA\VBA7\VBE7.DLL

ReportID: c27b19c9-7a37-11e1-92e0-8c736e7aadb9

Additional info:

Debugging the program showed failure in db connection using ADO

Please help me if you have any workaround for this.

Thanks

• Edited by Yujibao Monday, April 02, 2012 3:45 AM

I had this exact issue -- and finally found that Access was crashing from right clicking to copy and paste instead of useing CTRL + C and V.  My 2 cents

• Proposed as answer by vDaN02 AM Monday, July 30, 2012 9:39 PM

I experienced the same problem. For what it's worth, the work-around also works on Access Project (.adp) files.

Also, note that the work-around listed at http:// support. microsoft. com /kb /2625046 /EN-US is in error. It neglects the call to MSAccess.exe.

OK, it appears I can't submit my reply until "we are able to verify your account"! You'll have to re-assemble the link if you want to know what page I am referring to.