msg Microsoft Access has stopped working

[Richard M]

I am working with Access 2010 and all of a sudden I get this error message when I click on an Event procedure to edit the code "Microsoft Access has stopped working." I have the protection code turned on with a password.

Since I cannot turn the password off and cannot get the code, I can't change a thing. I have done the following with no results.

1. Compact and repair
2. Repaired the Office Access program
3. Open in Exclusive and checked everything I could do.
4. Somehow I got back into the code and made changes and then close the db. Now I am back to the message "Microsoft Access has stopped working."

Can anybody help me and tell me what to do next?

Richard

 

[mdlueck]

Are you saying that you turned on the password protection and right after that change this error started?

It sounds like Windows thinks that Access is not responding, so it is bringing up its "Crash Protection" window.

Did you make backup copies of the database? Like before you put on the password / started getting the "not responding message"?

 

[vbaInet]

It sounds application instability or corruption. My suspect is the latter though.

Try one of two things:

1. Create a new blank Access 2010 database. I'm assuming that we're dealing with an Access 2010 db (i.e. an accdb)
2. Import all your objects into it (and don't forget to tick the import specs and toolbars/menubars in the import wiard, i.e. if you had them)
3. Now try it in this new db

Or

1. From the new db shell above, save your form as text:

SaveAsText acForm, "FormName", "\FullPathToTextFile.txt"

2. Delete the form, Debug > Compile, Compact & Repair
3. Load the form from the file

LoadFromText acForm, "FormName", "\FullPathToTextFile.txt"

4. Debug > Compile
5. Now try going to the VBA editor (Note: You can get the code from the text file too)

 

[Richard M]

Yes I am using Windows 7 and MS Office 2010

Here are the steps I have taken after posting this thread:

1. Looked at the VBA code editor and could not open it.
2. Looked on the Internet and found a possible solution. This is to go to options/Add-ins/Goto and delete any wierd add-ins. There was none.
3. Opened the db and checked on the problem form and the after update event ,event procedure, it opened.
4. Removed the password protection (it was on for the last 2 to 4 weeks)
5. Deleted the code in the after update event.
6. Saved and closed the db.
7. Opened the db and opened the form that was giving me a problem and looked at the Open event, event procedure, and there it was. Checked several others and all was ok.
8. Closed the db several time and opened it agin and all was ok. Even tried rebooting the computer and again all was ok.
9. If this problems re-occures I will then reload Office 2010 and then look at rebuilding the db. I will also look at this thread to help me with the form in question.

Thanks for the help,

Richard

 

[Richard M]

The problem poped up again and I cannot view the event procedures. I even looked at the last backup and could not see the event procedure code. I am going to re-install MS office 2010.

If anybody have different ideas, please let me know.

One other question is how to convert this back to 2007 and let it run in 2010?

Richad

 

[vbaInet]

You didn't follow any of my steps did you?

 

[gemma-the-husky]

and what you need to do is what vbainet said

create a new empty database, and try to import everything into the new database.

then make sure the front end/back end is split if not already, and keep a safe copy of the front end in the event of any future corruption

 

[Richard M]

Hi Everybody,

I just started to create a new a new database when I came across a word "decompile". I went to the Access help and found that sometimes bits of code (you do not see) is left when deleting code or changing code. So I decomplied the database and then did a complie and my code came back when I clicked on the event procedure.

I put the following code in the Run box and that opened access and allowed me to select the database I wanted to decompile. After it was done, the database opened up and I opended the VBA editor and performed a compile. All the problems were gone and I could write code again.

It took me a couple tries because MSAccess.exe was not where the sample code said it was.

"C:\Program Files (x86)\Microsoft Office\Office14\Msaccess.exe" /decompile

If I continue to have problems and the above stops working, then I will rebuild the database.

Thanks for staying with me,

Richard

 

[Kiwiman]

Howzit

You will probably find that it has got nothing wahtsoever to do with the database you created, but a problem with SP1 that MS are aware of. I get the same thing all the time once this SP updated. Rather anoying to put it mildly. The link below has the work around you used. You pretty much have to remember to compile your code all the time.

There appears to be a hotfix to this issue in the link below... I haven't tried it as yet.



http://answers.microsoft.com/en-us/office/forum/office_2010-access/access-2010-sp1-you-receive-random-crashes-in/d2bf6175-075a-4a12-a2b1-f55d40af271b

 

[Richard M]

I have read that the hotfix could create more problems. I have look for the SP1 on my computer and cannot find where it was updated to my computer. So if it does, then I will look at other approach. Maybe I will stick with 2007 and just install it on comuters using 2010.

Richard