Share via

ACCESS Crashes

Anonymous
2011-10-18T20:09:43+00:00

I was designing a form in ACCESS 2010 this morning and everything was going fine.  I logged out of the database because one of the users need to make a data entry.  They opened the database, made their entry, and logged out normally.  When I went tried logging back into the database, it starts and about 25 seconds later I getsa 'Not Responding' Error and the application closes.  When I click on 'More Details' this is what is provided.   

Problem signature:   Problem Event

Name:    APPCRASH  

Application Name:    MSACCESS.EXE  

Application Version:    14.0.6024.1000  

Application Timestamp:    4d83e4fc  

Fault Module Name:    VBE7.DLL  

Fault Module Version:    7.0.16.19  

Fault Module Timestamp:    4d430aec  

Exception Code:    c0000005  

Exception Offset:    00023081  

OS Version:    6.1.7601.2.1.0.256.1  

Locale ID:    1033 

Additional information about the problem:  

LCID:    1033  

skulcid:    103

Anybody have any clue what is going on?

Jeff

Microsoft 365 and Office | Access | For home | Windows

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

Answer accepted by question author

ScottGem 68,830 Reputation points Volunteer Moderator
2011-10-18T20:28:33+00:00

First, you should NEVER have to exit out of an app to allow a user to do data entry. That you had to do that indicates your environment is not designed properly. Your app should be split between a back end (the tables) and a front end (everything else). The back end is then stored on a network share while the front end is stored locally on each user's machine. At the least you have a production front end stored on the network. 

Then you have a development front end. THAT is where you make all your changes, test them, make sure they work properly and THEN put the new front end into production.

Now to answer your question, did you try doing a compact and repair? Having a single file for an app is an invitation to corruption. The only thing I can tell from that info, is the crash probably occurred running some VBA code. Try the Compact and repair, then split the app and set it up properly.

Was this answer helpful?

6 people found this answer helpful.
0 comments No comments

Answer accepted by question author

Anonymous
2011-10-19T21:21:00+00:00

In addition to Scott’s recommendations, I would also recommend reviewing the following KB article and thread:

2625046 Access 2010 crashes in VBE7.DLL after installing Office 2010 SP1

http://support.microsoft.com/default.aspx?scid=kb;EN-US;2625046

Access 2010 SP1 – You receive random crashes in certain database or when opening the VBA window in those databases after installing Office 2010 SP1 - http://answers.microsoft.com/en-us/office/forum/office_2010-access/access-2010-sp1-you-receive-random-crashes-in/d2bf6175-075a-4a12-a2b1-f55d40af271b

Best Regards,

Nathan O.

Microsoft Online Community Support

Was this answer helpful?

1 person found this answer helpful.
0 comments No comments

0 additional answers

Sort by: Most helpful