APPCRASH error in Access 2010

[Lynn Cohen]

I manage an Access 2010 database that is split to accommodate a multi-user environment. It's a pretty simply-structured database and generally doesn't give us problems. BTW, I'm not a programmer; just a pretty competent user.

In the past month I and other users been getting APPCRASH errors when exiting the database. My Help Desk folks are stumped. They've reinstalled the application on my system, and a week later, ran Office 2010 repair, and it's still happening. Nothing about the database structure has changed. Here's the detail of the problem.

Problem Event Name: APPCRASH


Application Name: MSACCESS.EXE
Application Version: 14.0.7104.5000
Application Timestamp: 51ce12c5
Fault Module Name: ACECORE.DLL
Fault Module Version: 14.0.7102.5000
Fault Module Timestamp: 519f61eb
Exception Code: c0000005
Exception Offset: 00000000000d6af6
OS Version: 6.1.7601.2.1.0.256.4
Locale ID: 1033

Additional information about the problem:
LCID: 1033
skulcid: 1033

Has anyone else run into this; and more importantly, have you been able to fix it, and how? I've seen threads here about other APPCRASH events, but can't seem to find a clear direction in which to go to get this fixed. Would appreciate any pointers.

Thanks!

[June7]

I've never even heard of this.

Bet you've already seen http://support.microsoft.com/kb/2279689

This is probably one of those issues that could have any number of causes. Finding the one that fits your situation is challenging.

What has changed with network in past few months? What do the users have in common? Does it happen everytime for everyone?

[NTC]

I would tend to drill down into a more precise definition of: "...when exiting the database..." and in particular if there is code being triggered on an object close or unload event......

[Lynn Cohen]

Thanks for the replies!

June7, It doesn't happen every time for everyone. I can't identify a pattern. Our Network people made some changes back in December. We generally understand that whatever they did had to do with increasing security on the network, but they haven't shared any more specific information. (Sidebar: That's really frustrating for many people.)

NTC, "when exiting the database" means clicking on the Close button (the X) at the upper right of the database window. Re: the issue of "code being triggered on an object close" etc. - I tend to doubt it. It's a *very* simple database containing just tables, queries, reports; there aren't even any lookup fields or subforms in this thing.

[June7]

If there is no code in any form or report Close or Unload events, the only other think I can suggest is to try importing everything to a new frontend and see if the issue persists.