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.
I'm glad to see that it's not an issue Scott and I are only having. My company has been rolling out 2013 to more and more users every day and it's been a growing concern for us. Best of luck finding a solution, Gina!!
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!
Yes, it did crash on that form and any form that uses that section of code but only when running in Access 2013, runs fine in Access 2010.
Arrhhh thank you, thank you.
I'm not the author of the code. I will have a play and see if I can work it out based on what I need it to do. Maybe I can comment block it and see what the results are.
As far as writing an alternative to these parts, It's way above my head. Generally, I can work out what is happening in the code but have trouble working out why. I do want to learn though.
The forms are intended to be used as a check list for the different components as named. Not all items in the list may be applicable which accounts for the result Not Inspected. The results are recorded back into the tables for later reference.
I comment blocked the looping section in the On Load event. I think that is where the problem is.
This part of the code brings the results back into the form to allow me to change Failed to Passed results hopefully, on the next visit to the property.
Yes, it did crash on that form and any form that uses that section of code but only when running in Access 2013, runs fine in Access 2010.
Scott,
It is definitely that section of code that is causing the problem. What exactly are you trying to do? Might have to rethink that section of code because it does not work consistently.
I also noticed your use of Reserved Words... Type and Reference, never a good idea.
HOWEVER, it runs perfectly in Access 2010, so it's definitely an Access 2013 issue and I truely don't know why.
EDIT: Okay, it's late and I have a meeting tomorrow. So, I'll play with this some more tomorrow during breaks!