MS Access 2013 crashes continually on different computers.

Sorry for the delay...  I just got the eMail that you replied!

1. Do you have both versions of Excel installed?  (You might want to use Late Binding for the Excel library, that way no worries about versions.)
2. What other DAO Libraries?  (If you are trying to set a Reference to the DAO Library you don't need to, it's included in the Microsoft Office Access database engine Object Library.)
3. Does each Module have...

Option Compare Database

Option Explicit

...at the very top.  If it does not you need to add it and Debug>RE-ompile to check for errors.

4. 32 bit Access or 64 bit Access?

Hi Gina,

I have the following references loaded:

• Visual Basic For Applications
• Microsoft Access 15.0 Object Library
• OLE Automation
• Microsoft Office Access database engine Object Library
• Microsoft Excel 15.0 Object Library

Although I do make references to DAO objects, I don't explicitly have the DAO Library Object reference set because:

1.  Each time I try it to set the reference, it gives me the following error (message box <!>):  Name conflicts with existing module, project, or object library.

2.  When I compile my code, I don't get an error regarding a missing reference.

I tried running the "Fix It for me" here (http://support.microsoft.com/kb/2019235) for Windows 7, but that didn't seem to work.

I'm running Windows 7 64bit, with Office 2013 Pro Plus 32 bit (upgraded from Office 2010 Pro Plus 32bit).

What References do you have set?

Thank you olb49.  I like the new 2013 updates to the look and feel that 2013 brings, but not nearly as much as I like being able to develop in Access on a platform that doesn't crash.

Hi Ben,

I've tried decompiling (following Tim and David's steps here http://stackoverflow.com/questions/3266542/ms-access-how-to-decompile-and-recompile) but the behaviour still persists.

Have you tried decompiling :

http://desmondoshiwambo.wordpress.com/2013/06/26/repairing-access-vba-corruption-using-decompile/