Microsoft Access has stopped working

[sawilliams]

I have an Access 2003 db that runs just fine in 2003. But my company has upgraded to Access 2010. I made many modifications to the db and it was fine until, for no apparent reason, Access relayed the message "Microsoft Access has stopped working". Then it says "A problem caused the program to stop working correctly etc." and Windows would try to find a solution but nothing happens. I found that I can move the db to another laptop and open it just fine in 2003. I researched online and it seems that this is not an uncommon problem. There are myriad possible causes/solutions that have been suggested, and I have tried them all (compact & repair, decompile, uncheck the Name AuutoCorrect boxes, set minimal references, compile, do double compacts, etc.) Still I have the same problem. I'm at my wit's end with it. Has anyone else been experiencing this, and if so, will you share your solution(s)?

 

[1DMF]

Yes, since installing SP1 for Access 2010, I have lost 3 hours work today, at regular intervals.

I have had to keep rolling back to another version as everything is fine, then suddenly while i'm working on the DB i get the stopped working message but then it won't open except in 'shift' mode but the code won't open and the DB is totally corrupted.

There is something seriously wrong with MS ACCESS 2010!

"In complete darkness we are all the same, only our knowledge and wisdom separates us, don't let your eyes deceive you."

"If a shortcut was meant to be easy, it wouldn't be a shortcut, it would be the way!"

MIME::Lite TLS Email Encryption - Perl v0.02 beta

 

[sawilliams]

Since I posted my problem, I have tried a few things. First, the db that won't open in Access 10 opens just fine in Access 2003 on my home laptop. I compacted it over and over again (someone advised me to do that). Before I brought it back to my Access 10 laptop, I did a repair on Office 10. When I open the db on my Access 10 laptop, it seems fine till I try to close it and then I get an error that "selected collating sequence is not supported", whatever that means. So, I tested it on third laptop, also running Access 10 and I got a bunch of MSCOMT2.OCX errors. I went to compile the db on the third laptop and the compiler found a whole bunch of errors. Yet, when I run the very same db on the original Access 10 laptop, the compiler runs without any errors and I get no MSCOMT2.OCX errors either. So, I think there is something very funky with my Office Suite in general. Powerpoint does weird stuff too, that no one has been able to explain.

The idea that I have to shuffle my Access 10 db back and forth between different computers to get it to run is really scary. I have to deploy this db shortly and I have to get the bugs out before I do.

 

[1DMF]

Well I solved the mixed office environment issue by installing MS Access 2010 runtime on all users machines, converting the DB from Access 2003 to Access 2007 version, then compiling it to an ACCDE and changing the ACCDE extension to ACCDR.

Also you have to rewrite all your office suite application object bindings to 'late binding' so it doesn't care what version of Word, Excel or Outlook the client is using, and although that OOM Guard is damn annoying in Outlook 2003, at least the trusted locations reg key works with Office Outlook 2010!

All deploymets have worked fine for many months until I installed SP1 for Office Pro 2010, perhaps coincidence, either way I am still experiencing some unexplained corruptions that I wasn't pri SP1.

Very frustrating indeed!

"In complete darkness we are all the same, only our knowledge and wisdom separates us, don't let your eyes deceive you."

"If a shortcut was meant to be easy, it wouldn't be a shortcut, it would be the way!"

MIME::Lite TLS Email Encryption - Perl v0.02 beta

 

[1DMF]

Well for those also experiencing this problem with Access 2010 i can confirm that uninstalling SP1 for Office 2010 resolved the issue.

I just lost the entire morning's work when the DB suddenly 'Access Has Stopped Working'.

Aftyer that point any attempt to open the DB just crashed with that error message.

Even opening it in devel mode (Shift Key), allowed you to open the DB but any attempt to edit the VBA code or a form, instantly crashed the DB.

Compact/Repair had no effect!

So I uninstalled SP1 and bingo the DB corrupt DB now opens fine and I have no longer lost the development done this morning - Phew!

As MS has changed the VB DLL in SP1, hence having to install SP1 on all client machines otherwise they could no longer run the compiled application!

And now removal of SP1 has magically fixed the corrupt DB, it's looking suspicously like a serious bug in SP1.

Anyone else having this problem?

"In complete darkness we are all the same, only our knowledge and wisdom separates us, don't let your eyes deceive you."

"If a shortcut was meant to be easy, it wouldn't be a shortcut, it would be the way!"

MIME::Lite TLS Email Encryption - Perl v0.02 beta

 

[sawilliams]

I have been experiencing continuing weird stuff but I find that if I put the corrupted db on a flash drive and open it on another computer running Office 2010, it needs compiling and returns some errors but it runs and does not crash. It really seems as if the problem is the version of Access I have on my laptop. Once I have opened and closed the db on another machine, and compacted it and compiled it, then I can return it to the problem laptop and it will run for quite a while before it crashes the app. I've been working successfully for about 4 hours.

I don't know if this is helpful. I wish we would hear from some other folks out there, if there is anyone else dealing with this issue.