none
Microsoft Access has stopped working

    Question

  • I have a large MS Access 2010 application fronting a 2005 SQL/Server database on a Windows 2003 Server.  This app has run fine for years on a Windows XP client and also on a windows 2003 server.  I recently upgraded my workstation which included a migration from Windows XP to Windows 7 and now I get the error "Microsoft Access has stopped working" when I try to launch the application.  This did not happen immediately after migrating but about a week later.

    The new PC is a 64bit as is Windows 7  -- but the Office 2010 suite is still x86. 

    Note that I can copy the application from the Window 7 machine to the Window 2003 machine and it works fine (hitting the same backend) -- so I am confident that the code is good.

    More Info...

    The problem only occurs when I have designated an auto-start Access form.  If I turn that off, I can launch the application OK and then (manually) run the self-same form without incident. 

    It is also worth noting that I have a second very large Access application running on the same PC and it also has an auto-start form -- but it is behaving correctly.

    Performing a compress/repair on the data base does not help ... nor does rebooting the PC ... nor does swearing :)

     

    Tuesday, February 01, 2011 9:28 PM

Answers

  • OK I think I fixed my own problem!  Earlier I was having similar difficulties with Visio abending whenever I tried to close it.  I did a search for that problem and found a solution posted on another forum.  I tried the same solution here for MS Access -- and it worked!. 

    Here it is ... In Access, under File>Options, go to Add-ins tab.  At the bottom of the screen there is a drop down labelled "Manage" and along side it, a button labeled "Go ...". 

    Press it! 

    After a warning about closing and re-opening the database, a COM Add-Ins widow pops up.  If it has an available Add-in "Send to Bluetooth" and the check box is checked this is your problem.  Uncheck it.  Save changes and cloase out of Access and relaunch.  et voila, it works!   

    • Marked as answer by Bruce Song Thursday, February 10, 2011 3:31 AM
    Tuesday, February 01, 2011 10:18 PM

All replies

  • OK I think I fixed my own problem!  Earlier I was having similar difficulties with Visio abending whenever I tried to close it.  I did a search for that problem and found a solution posted on another forum.  I tried the same solution here for MS Access -- and it worked!. 

    Here it is ... In Access, under File>Options, go to Add-ins tab.  At the bottom of the screen there is a drop down labelled "Manage" and along side it, a button labeled "Go ...". 

    Press it! 

    After a warning about closing and re-opening the database, a COM Add-Ins widow pops up.  If it has an available Add-in "Send to Bluetooth" and the check box is checked this is your problem.  Uncheck it.  Save changes and cloase out of Access and relaunch.  et voila, it works!   

    • Marked as answer by Bruce Song Thursday, February 10, 2011 3:31 AM
    Tuesday, February 01, 2011 10:18 PM
  • Hello,

    Did you try to compile your code on a new computer in Access 2010?. What version of Access the app was originally developed?

    Nadia

    Wednesday, February 02, 2011 2:07 AM
  • Hi Bjshuett,

    It seems that you have resolved your issue yourself. I have marked your reply as the answer and thank you for your feedback of your issue. You are more warmhearted if you take time to reply NadiaSz.

    You are welcome.

    Best Regards,


    Bruce Song [MSFT]
    MSDN Community Support | Feedback to us
    Get or Request Code Sample from Microsoft
    Please remember to mark the replies as answers if they help and unmark them if they provide no help.

    Thursday, February 10, 2011 3:35 AM
  • Well done bjshuett - I had the same problem and you're suggestion cracked it.

     

    thanks

    Tuesday, April 26, 2011 10:17 AM
  • Hello,

    I tried solution posted here and it does not work, as I do not have any COM Add-Ins and therefore cannot uncheck "Send to Bluettoth" check box.  Does anyone has any other solutions?

     

    • Proposed as answer by GatorGirl1989 Wednesday, July 20, 2011 4:37 PM
    • Unproposed as answer by GatorGirl1989 Wednesday, July 20, 2011 4:37 PM
    Monday, June 20, 2011 2:50 PM
  • Hi,

    It seems that all that is necessary is to run the COM Add-Ins as I don't have any installed either but now my database is working again. Ahhh, the mysteries of life.

    Tuesday, July 19, 2011 10:59 AM
  • Access 2010 stooped wording for me after I downloaded the service pack to try to fix Word 2010 that had stopped working.  As it appeared to be a compatibility issue, I did the following and am now able to access my files and get my work done.j  Good luck!

    Start

    Right click on Access or Word

    Click on Properties

    Select the Compatibility Tab

    Click on “Run this program in compatibility mode for:  Windows XP (Service Pack 3)”

    Receive a message to run, select yes

     

    Wednesday, July 20, 2011 4:38 PM
  • Didn't work same problem, no Bluetooth on com add-in, that option didn't work either.

    Can open other forms

    Will test delete rebuild command buttons, later.  Have wasted enough time on this so far.  Tried roll-back to .mdb, failed.  This makes Access 2010 just about unusable at this point--this is key application and I can't find a way to even open it without it crashing.

     

    Sunday, July 31, 2011 6:01 PM
  • Did not work for me, exactly the same problem, no bluetooth add-in but unchecking the 1 com addin I saw didn not work.  The other answer below did not work either.
    Sunday, July 31, 2011 6:02 PM
  • I also have been having a similar problem with win 7 64bit and Access 2010.   The application itself is not large 300k, with data it is 80M.   Access loads and and about 15 seconds the ACCESS HAS STOPPED WORKING message appears.   I have also tried all the option above with no success.  Like all the others on this thread, I am looking for solution.   I need the database working.   As a side note the database worked on my other win xp with Access 2003.   Any ideas will be greatly appreciated.   Thanks in advance for the assistance. 
    Tuesday, September 06, 2011 9:32 PM
  • For me, running 2010 on a 64 bit Windows 7 system, the issue seems to be dormant for awhile, then crop up again after I've made a code change.  Not every code change, just occasional.  The change can be large or small.

    So, I'm now keeping many backups and I make sure to copy the dbase immediately before any code change.  If the error occurs, I restore the backup, re-copy and try again. 


    • Edited by mmwilcox Thursday, October 06, 2011 5:00 PM
    Thursday, October 06, 2011 4:59 PM
  • I faced more or less the same problem; MS Access 2010 32bit on Windows 7 64bit OS. In my Win7 I have a virtual machine running WinXP + Office 2003. When I open the MS Access file there and perform a compact&repair, this solves the problem in 99% of the cases. I can then re-open the file again in Office 2010. The last time I was missing a reference, when I fixed this in 2003, the file worked again in 2010.

    Cheers,

    Fokko


    ALM/TFS Consultant, Software Developer C#.NET, SQL Server specialist at Delta-N BV (http://www.delta-n.nl)
    Friday, October 07, 2011 12:12 PM
  • I'm having the same issues with Access 2010 32bit on Win7 64bit.  Disabling Add-Ins fixed the crashing once, but it immediately came back the next time I opened a file.  Running in WinXP (SP3) compatibility mode didn't resolve my issues.  Access continues to crash.  I cannot believe that I'm going to have to run Access 2010 in the virtual XP windows.  Where is Microsoft on this "MAJOR" issue. 

    P.S. If I hold down the SHIFT key while opening a file, I can work in Access with no issues until I try to enter VBA.  That's when Access crashes.


    • Edited by BigKahuna52 Saturday, October 08, 2011 10:28 AM
    • Proposed as answer by NigelV1 Monday, October 10, 2011 11:50 AM
    Saturday, October 08, 2011 10:19 AM
  • The solution I have found to this is to open the database using the Decompile option:

     

    "C:\Program Files\Microsoft Office\Office14\MSACCESS.EXE" "C:\MyAccess.accdb" /decompile

    where MyAccess is the name of your Database. The Database then opens, and you can compact and repair at your leisure.

    To save time (because this seems to happen quite frequently with me), save the above in Notepad as a .bat file. Then just Double Clicking on the file will bring your Database back to life.

    I suspect the problem is due to uncompiled VBA Modules, but I have no proof of this

    • Proposed as answer by tinashem Tuesday, June 04, 2013 1:25 AM
    Monday, October 10, 2011 11:59 AM
  • I have been fighting this for months like the rest of you.  I use Windows 7 on 64 and 32 bit pc's.  My MsAccess app is 27 mb for the front-end and last night I back up to a jump drive.  This morning on my Win 7 pc I got the message of death that we are all fighting "MSAccess stopped running".  I loaded on Windows 2003 server from my jump drive and it worked ok.   I loaded on my laptop Win 7 and it crashed.

    I used the above decompile option it and I WAS ABLE TO USE THE SAME CODE FROM LAST NIGHT AND IT IS WORKING.  I hope I am not speaking to soon.  The only way that I could get it to work was in the CMD window change the directory to Office14 and key in  

         msaccess.exe /decompile

    This will bring up the MSAccess window.  On the left pick your ACCB that you want to open while Holding Down the Right Shift Key.  

    Go to VBA window and under the debug menu select the compile function.

     

    Jim

    Friday, October 14, 2011 7:13 PM
  • Hi jspeta and NigelV1

    Want to say thank you. Since having to upgrade to Access 2010 from Access 2000 I have had this 

    Microsoft Access has stopped working 

    problem.

    Can't believe MS are not aware of it and corrected it.

    Still you have both given me a work around that WORKS!

    Many thanks

    mapline

    Sunday, October 16, 2011 10:30 PM
  • Had this problem since we upgraded to Office 2010 from the 2007 version. Our access application has a frontend of 20MB, and a backend on an SQL2005 (now trying to pass on 2008). I solved my problem after reading a lot... I opened up my Access application by pressing the Shift button, so I bypassed all startup forms and logins. Opened up a module, not a particular one! Went on Debug>Compile <ProjectName> and voila...problematic old code started firing up error messages. After I removed all the unnecessary parts of the code and changed with new refs/code the needed ones I closed and reopened. The database opened like a charm. I compacted and repair since this process made my db frontend went on 90MB and started working again with no problem. Hope it works for you as well. Have a good day.
    • Proposed as answer by Chrysostomos Tuesday, October 18, 2011 6:59 AM
    Tuesday, October 18, 2011 6:53 AM
  • The solution I have found to this is to open the database using the Decompile option:

     

    "C:\Program Files\Microsoft Office\Office14\MSACCESS.EXE" "C:\MyAccess.accdb" /decompile

    where MyAccess is the name of your Database. The Database then opens, and you can compact and repair at your leisure.

    To save time (because this seems to happen quite frequently with me), save the above in Notepad as a .bat file. Then just Double Clicking on the file will bring your Database back to life.

    I suspect the problem is due to uncompiled VBA Modules, but I have no proof of this

    Hi,

    I had a similar issue - access crashing whenever tried to open a form or a module - the decompile trick worked. I was a little worried because I had backup only for data not for the design part...

    Thanks.

    • Proposed as answer by Chrysostomos Thursday, October 20, 2011 10:39 AM
    Wednesday, October 19, 2011 10:46 AM
  • The solution above posted from another user, regarding the decomplilation, is also posted by Microsoft on September 30,2011 on

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

    However, till the time the issue with the Faulting module vbe7.dll is resolved, we have to figure out a way to to manage our access dbs since no matter what you do, even if you just make a new form the problem still comes back.

    When you access db frontends are in production we need a SOLUTION asap!

     

    PS. Have pending 12 Modules and modifications that I need to make in my access frontend and I cannot... :(


    CP
    • Proposed as answer by Firefly Joe Wednesday, November 16, 2011 3:02 PM
    Thursday, October 20, 2011 10:50 AM
  • I have this same issue running Office 2003 on Windows 7 machines.  One specific form in particular seems to be the problem.  Using the above method (/decompile) I can get it to go, but I'm looking for a real solution, or at least explanation!  Database works completely fine on XP machines, Server 2003 machines, etc., just no Windows 7.

    Hoping for a fix on this soon.

    Thursday, October 20, 2011 6:51 PM
  • I cannot thank you enough.  You saved me several hours of work.  
    Tuesday, October 25, 2011 1:37 PM
  • I have experienced a similar problem and have found a way to fix it which might be useful for others. 

    I get the "Microsoft Access has stopped working" message when I try to open any of my modules. The rest of the database opens fine however I can't open any modules. Simply saving the database with a different name fixes the problem. The problem arises if the database is closed while running code. For example, I accidentally created an endless loop in my code and closed the database while the code was running. Next time I opened it, I got the "stopped working" message. 

    Tuesday, November 01, 2011 11:18 PM
  • It appears that far too many people are experiencing the same or similar problems with MS Access and Windows 7.  I have tracked this problem down to the Startup option in Access.  If a form is designated to display at startup, Access becomes unstable.  The issue that occurs is that many, if not all, tables become unaccessible.  If an attempt is made to open a table in datasheet view, the system will crash.  The same goes if you try to query a table.  You can open the table in design view without consequence, but that's about it. 

    Bypassing the startup seems to eliviate this situation. 

    I have tried many other suggested solutions, including decompiling, etc..  The only thing that seems to work is the above.  I haven't tried going back to using an autoexec macro to display an initial form at run-time.  I'll post back if that works.

    Microsoft should really feel shame at this point, but they surely don't.  Win 7 is crap, Office 07-2010... crap too!!!

    Folks, take a look around, they think we're juviniles with the need for the big pretty pictures, cutsie objects, and really big letters, kind of like the big alphabet blocks you had as a child.  What a mess they are making of the working tools we use to accomplish professional business. 

    It's a good thing they aren't responsible for construction tools, god knows what a carpenter, electrician, or otherwise would do with cutsie / pretty hammers, drivers, and saws. :):):)

    Friday, November 11, 2011 3:40 AM
  • It's confirmed, any automatic startup options set to launch upon opening Access, be it a form designated in the Startup options, or a macro, will cause Access to crash when accessing table data.  This must be some security issue in Windows 7 interfering with Microsoft Access. 

    Pardon me for saying so, but what a freekin mess Microsoft has made!  XP was probably the most stable OS along with Office 2003.  Beyond that, I wouldn't give a nickel for the crap they've shoveled out recently.  All the oversized junk and nifty features they've introduced into the latest apps, including the rediculous ribbons, and yet all these problems prevailing, just proves that you can't polish a turd, no matter how hard you try.

    • Proposed as answer by Firefly Joe Wednesday, November 16, 2011 2:56 PM
    • Unproposed as answer by Firefly Joe Wednesday, November 16, 2011 2:57 PM
    Friday, November 11, 2011 4:19 AM
  • This catastrophic failure has happened 4 times to me - only to me the developer not to my users.

    Actions:

    1st time: Copied back-up and re-applied changes to database from change log. NOT A SOLUTION

    2nd and 3rd time: Re-installed Office 2010. NOT AN EFFICIENT SOLUTION

    4th time: Copied front end from my PC to my server and runs fine - copied back to my PC - runs fine! I DO NOT UNDERSTAND WHY this worked but it did! NOT A SOLUTION

    FINAL SOLUTION: Re-read this thread - THANKS TO CHRYSOSTOMOS - clicked on the link to the workaround - a hot fix is now available - installed hot fix and "corrupted" front end runs!

    If the failure happens again, I will post again. Thanks to all!

     

    Wednesday, November 16, 2011 3:12 PM
  • Hope you feel better for venting MPM01, but most of your comments are not all that helpful towards solving any problems.  Its just adds material for the rest of to read hoping there's something useful in there. 

    You might consider writing your own program - Win 7, Office, etc. - since you hate these so much.  These program are the lifeblood of my distribution business and i'm thankful to live and work in a time with these tools available.

    Thursday, November 17, 2011 10:34 PM
  • This evil error has happened to me much to often! My only real solution is to keep vigilant backups in multiple places. Usually I can find one that doesn't crash... :S

    However, there is one workaround that sometimes works for me that hasn't been mentioned here..... If I re-name the front end it will sometimes open without issue.

    As for the why of it all.... I haven't the slightest idea.    

     

    Just something to throw out there for my fellow frustrated developers :)

    Friday, November 18, 2011 2:45 PM
  • THANK YOU!!!!

    finally a way to tackle this "stop working" "undo VB code" thing

    Monday, December 05, 2011 10:08 AM
  • Salve!  I created a profile here just to say thank you!  I didn't know about the shift-open trick - that does work.  The decompile trick worked for me, too!  My accdb opens up now just like it is supposed to.

    I had the problem that if I tried to do compact & repair, Access 2010 (on xp sp3! not W7!) would go into an endless loop of c&r-restart until I opted not to repair, in which case it would just quit.  There looked like no hope except to purchase one of those hundred access-repair tools, of which there is absolutley no freeware ones (everybody wants money, you know). 

    So I started searching for how to do it manually, even if it meant opening the file with a hex editor!  That's how I found this thread.

    The shift-open method and the /decompile method  were my solutions.

    Thanks to y'all for working this out!  Livesavers!

    Tuesday, December 20, 2011 10:30 PM
  • Microsoft has released an Office 2010 patch on 12/12/2011 which is the ultimate solution to this problem.  This patch worked great for me (even repairing the previous corrupted databases without the need to decompile).

    The patch (both 32 and 64 bit) can be found at:

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

    Thanks to Chrysostomos for his lead on this.

     

     

     

    Wednesday, January 11, 2012 8:48 PM
  • Thank you NigelV1!  I had been testing some VBA code, but ultimately deleted the code so I never compiled anything.  So I decided to try compiling the blank code page and walah - no more error messages when I load the form :)  
    Wednesday, July 18, 2012 8:16 PM
  • Thank you!  That worked for me.  I just hope I don't have to do this to every single database.
    Thursday, July 26, 2012 6:05 PM
  • Thank you!  MS is trying to make the programs so "dummy" proof, that people who actually know how to use the programs aren't able to!  Very frustrating.
    Thursday, July 26, 2012 6:34 PM
  • Hi,

    I have the exact same problem, but your solution doesn't work for me: I don't have any Add-ins listed as available, let alone checked.

    Any other possible solutions, or even ideas about what the problem might be?

    The other thing is, this problem hits my database only intermittently.  Sometimes it works fine, but the next time it doesn't: I get that very helpful (not!) message "Access has stopped working..."

    Much appreciate any ideas anyone might have.

    Friday, June 21, 2013 12:37 PM
  • I originally developed my application in an earlier version of MS Access, possibly even MS Access 1997, and have ported the code to the new versions as they came out.


    Friday, June 21, 2013 12:39 PM
  • That worked beautifully!  THANKS!


    Gary Michalske

    Wednesday, October 23, 2013 11:56 AM