Ms Access has stopped working?

[Cyd44]

I have been working on my database and have added a new form and changed some other code. When I now enter the database and open the form in design view and try to look at my VBA code I get the error:-

MS Access has Stopped Working......etc and the application closes diwn.

I have saved copies of earlier versions prior to the new code and these work OK so I suspect it is to do with something I have added since. I have looked on the web and cannot get any sensible answer as to why it keeps crashing.

Does anyone have any answer to this please

I am using Set.Focus on my new form and am wondering if this might be the cause of the problem?

[NeoPa]

I would suggest starting by using the Bypass key (Shift) while opening the database. You may have a corruption, but we need info to start with. A full exact copy of the error message would be the next thing to post. If it gives a Debug option then select that and post the code it is stopped at along with the full error message.

[Cyd44]

I am not sure what you mean by using Bypass key. I went to database and pressed Shift Enter but all I got was the MS error message Access has stopped working. I have tried the earlier versions and it is also happening with these now so the problem seems to have migrated

[Cyd44]

Hi NeoPa,

I suspected that this was an application problem rather than a database one so this is what I did which appears to have resolved my issue :

I went to Control Panel and chose Remove Program option. I then chose MS OFFICE and Change option which gave me an opportunity to Repair Office. This took about 30 mins but did not give me any clues about what it found or repaired. It Simply told me the Repair was complete!
Once I rebooted I was able to run Access with my database.

On another note, I read your recommended info on Mandatory Variable Declaration and I noted that many of my Class Modules did not contain Option Explicit, so I have entered this declaration into those.

The upshot is that my database is running OK (at the moment at least).

[NeoPa]

Cyd44:
I had suspected that this was an application problem rather than a dbase one so this is what I did which appears to have resolved my issue.

That was clever. I wouldn't have thought of that. Congratulations on finding your solution.

I'm going to edit that post for typos etc so you can go ahead and mark it as Best Answer (Unusual for posts by the OP but appropriate in this case I think).

[Cyd44]

Thanks for the compliment. I thought I would put the resolution onto the forum just in case anyone else encountered a similar problem. I hope that is acceptable.

[NeoPa]

Perfectly so. We encourage it in fact ;-)