APPCRASH Access 2010 running macros

I have a ~300 line macro in Access 2010 that runs nightly that pulls information from from sqlserver 2008R2 via odbc (32bit)  and emails ~ 100 different reports.

At least once a week it hangs at different points in the macro with the same "Microsoft Access has stopped working" message (see below).  This has been occurring for the past 3 years (since I installed 2010) and have been patching at least once a week (hoping the problem would go away).

Also, I reboot the computer every night before the macro is ran.

Problem Event Name: APPCRASH
Application Name: MSACCESS.EXE
Application Version: 14.0.7104.5000
Application Timestamp: 51ce12f7
Fault Module Name: olmapi32.dll
Fault Module Timestamp: 522a335e
Exception Code: c0000005
Exception Offset: 002989cc
OS Version: 6.1.7601.2.1.256.48
Local ID: 1033
BFanguyAsked:
Who is Participating?

Improve company productivity with a Business Account.Sign Up

x
 
Bill RossConnect With a Mentor Commented:
Hi,

I would suggest that you convert the macro to VBA.  Macros do not have any method to trap errors.  You can do that in VBA and solve the issue much quicker.

If that's not an option then break the macro up into multiples and the message on the screen may give a clue as to which one fails.

Regards,

Bill
0
 
BFanguyAuthor Commented:
converting to vba is not an option, I believe it is the 32bit odbc driver locking up.
0
 
Bill RossCommented:
What version of Windows - 32 or 64 bit?

Why not convert to VBA?  Just so I understand.

Regards,

Bill
0
Get 10% Off Your First Squarespace Website

Ready to showcase your work, publish content or promote your business online? With Squarespace’s award-winning templates and 24/7 customer service, getting started is simple. Head to Squarespace.com and use offer code ‘EXPERTS’ to get 10% off your first purchase.

 
Scott McDaniel (Microsoft Access MVP - EE MVE )Infotrakker SoftwareCommented:
I believe it is the 32bit odbc driver locking up.
What leads you to this assumption? The error above indicates "olmapi32.dll", which is associated with email.

What does your macro do?

FWIW, running unattended operations which rely on macros is fraught with issues. As BillDenver suggests, convert this to VBA, which allows you to actually manage errors, and you'll resolve this much more quickly.
0
 
BFanguyAuthor Commented:
Will try converting to vba.
0
 
BFanguyAuthor Commented:
Converted to vba.

Still get:

Problem Event Name: APPCRASH
 Application Name: MSACCESS.EXE
 Application Version: 14.0.7104.5000
 Application Timestamp: 51ce12f7
 Fault Module Name: olmapi32.dll
 Fault Module Timestamp: 522a335e
 Exception Code: c0000005
 Exception Offset: 002989cc
 OS Version: 6.1.7601.2.1.256.48
 Local ID: 1033
0
 
Scott McDaniel (Microsoft Access MVP - EE MVE )Infotrakker SoftwareCommented:
Then I'd suggest you have issues with your email system, since the "fault module name" is olmapi32.dll. You might try repairing or reinstalling Outlook.
0
 
BFanguyAuthor Commented:
Thanks Scott.

I failed to mention, I had reinstalled Outlook after changing from a macro to vba.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.