MS Access 2013 crashes continually on different computers.

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.

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!

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.