debugging access 2013 crash

[DKP]

I'm trying to make modifications to an existing Access 2013 database on Windows 8. For the most part things are working as expected, however, when iterating through a recordset via a form it crashes Access from time to time w/ the following output. I assume this is something I'm doing in my code, but w/o getting a decent stack trace it's difficult to know what the problem is. Is there any way to obtain any more useful debug information so that I can try to track this issue down?

Problem signature:
Problem Event Name: APPCRASH
Application Name: MSACCESS.EXE
Application Version: 15.0.4649.1000
Application Timestamp: 53e9a3eb
Fault Module Name: acedao.dll
Fault Module Version: 15.0.4641.1000
Fault Module Timestamp: 53c5c260
Exception Code: c0000005


Exception Offset: 0004a979
OS Version: 6.3.9600.2.0.0.768.101
Locale ID: 1033

[ranman256]

This is not the code. (sorta) I get these occasionaly on certain PCs but works on others.
Compress /repair the old db.
Create a new blank db.
Then import EVERYTING....all forms, tbls, reports, modules, etc from the old one.
The usually stops the crashing.

[John_G]

Hi -

You might also want to replace the offending module acedao.dll with a fresh copy if you can. It's unlikely, but it could be corrupted.

[DKP]

This is not the code. (sorta) I get these occasionaly on certain PCs but works on others.
Compress /repair the old db.
Create a new blank db.
Then import EVERYTING....all forms, tbls, reports, modules, etc from the old one.
The usually stops the crashing.

Thanks for the suggestion. This really sounded promising, but I tried it w/ same result. Any other ideas? Is there anyway to get Access to give you a meaningful call stack when it crashes so I can know the last line of my code that was executed? If it's something I'm doing, maybe that would help me to isolate the issue.

[John_G]

Do you make sure to compile your code each time you change it? If not, open any module, then Debug - Compile.

Did you try re-installing Access, in case there is corruption somewhere?

john

[DKP]

It looks like there may be some issue w/ Windows 8 / Access 2013. I tested the original database on the target system (Windows 7 / Access 2013) and it works fine. I copied the same database to my system w/o modification and I get the same crash. I also tried running the database on another Windows 8 / Access 2013 system and see the same thing. In any case, it seems to working on the target system, which is the important thing.

Thanks to those who offered suggestions.

[drexasaurus]

Also consider decompiling (done from command line, http://www.fmsinc.com/microsoftacces...Convention.asp). Note that I always do it from the machine with the oldest operating system that the database is going to be run on--I've had issues where the database didn't run on older operating systems after I decompiled it on a more modern one (does not seem to apply in this case tho).