This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
I having increasing problems with Access 2013 crashing. Even after compacting and repairing the database it crashes all of the time - now it's crashing whenever I try to do a "save as" or when I try to exit. It's been unstable since I started using it but it seems to be getting worse, and it happens on multiple machines. Anyone have an idea why it's constantly crashing?
A family of Microsoft relational database management systems designed for ease of use.
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.
Keith,
Well, turning out to be the code is still a bit of an issue, especially because it works in Access 2010. Good code should work anywhere!
Yep. it's that On_Load event code that is causing the problem. Still driving me crazy because it works in Access 2010 but as soon as you open in Access 2013 it crashes. I have moved it to the On_Open event and the On_Current event with the same results... very frustrating. I'm in a meeting with a Client today so not sure how much playing I can do but will be looking tonight for sure... It's almost becoming a mission to figure out why!
Hello Gina,
On the 11-02-2014 in my desperation to get a working database I bought a stand alone version of MS Access 2013 in the slim hope that there may have been something different in it to the version I'm running. As we are now aware from the work you have done it didn't work. Still crashes with those forms. It looks to be the loop procedure that 2013 doesn't like.
Would you have had the opportunity to look at it again after your meeting?
Is there some hope that 2013 is going to work for me?
Should I look for Access 2010?
I need to use other components of the Office suite, so if I were able to find Access 2010, would it work in conjunction with Office 365? I saw in an article that said Office 2013 and Access 2010 work together if you install 2010 first then Office over the top. Wouldn't Access then be upgraded by to the 2013 version? Particularly as I'm using Office 365, I don't think there were options given to which components you installed.
Scott,
Got tied up with Clients but I have not abandoned this because it makes no sense and has kind of becone a mission! Access 2010 will not integrate with Office 365 so the goal is to get it working in Access 2013. That being said, you are making a stand alone database so what does Office 365 have to do with anything?
Scott,
Got tied up with Clients but I have not abandoned this because it makes no sense and has kind of becone a mission! Access 2010 will not integrate with Office 365 so the goal is to get it working in Access 2013. That being said, you are making a stand alone database so what does Office 365 have to do with anything?
Thanks Gina,
I appreciate that mine would not be the only problem you have and I am very grateful for your time. Please do not think that I'm impatient or take any of my comments as being any sarcastic. I'm new to Access and may not be communicating things properly and my thoughts may seem irrational to you.
I mentioned Office because I have business type templates set up in Outlook that I would like to use when I send Reports to clients as attachments, that's all. Looking on the positive side, when you get the Database working for me, then everything will be roses and nothing else will need to be a consideration, except I won't be able to thank you enough.
I have now asked for help because I cannot figure the reason. Hopefully, he will find something I missed!