The Mysterious Death of Access

[Ian Wright]

I created a database that opens with a switch board that operates off buttons. This worked perfectly okay until one button, opening a form, caused Access to die.
Nothing had changed and if you go into another button of the main switchboard and then the problem button the problem button works fine. Below are the two msgs that the fail produces. Any ideas?

"Microsoft Office has stopped working
Windows is checking for a solution to this problem"

Followed by:

"Microsoft Office has stopped working
A problem caused the program to stop working properly
Windows will stop the program and notify you if there a solution is available"

Needless to say, it doesn't

Any ideas folk please?

 

[CJ_London]

'nothing has changed', well something has. If you've not had any windows updates, most likely the db has become corrupted. so decompile, compact and repair.

if that does not solve the problem, provide more information - code in your navigation form, code in the opening events of the forms being opened. description of the db - what version? is it split? multi user? working over a wireless network? etc

 

[Ian Wright]

Thanks for your kind reply, as a novice I do need pointing in the right direction,

Ian

 

[CJ_London]

sorry - do you still require help? I can't provide any more help unless you answer my questions

 

[Ian Wright]

Hi CJ, I will take your advise, rebuild and compile etc and if that is no good, I'll come back to you. Many thanks, Ian

 

[Ian Wright]

Just an update.

I had done some buttons by building with VBA statements and others by command wizard. I rebuilt all by the command wizard and not had a problem since.

 

[The_Doc_Man]

Yep, the wizards are typically as dumb as a box of rocks, too dumb to have ulterior motives or stray thoughts like us unreliable people do. For what it is worth, that behavior is often a sign of a loop.

If you have a multi-CPU system or a multi-core system, you would be able to open the task manager and see if MS Access is saturating one of your cores or one of your CPUs. If, for example, you have 4 cores, each one contributes 25% to the available time shown under the Pct Idle column of TM. IF you have a VBA loop, MSACCESS.EXE will show 25% for that case. (If you have other than 4 possible threads,the percentage will be different.) If TM shows that Access is filling up one of the potential CPU threads, odds are that you built a non-ending loop.

 

[Ranman256]

I've had one do this on 1 PC. No matter what I did ,it would not repair.
I had to create a blank db, then import EVERYTHING.

 

[gemma-the-husky]

it happens.

I opened a database that had been working properly a few days ago, and half the stuff wouldn't work due to corruptions.

I keep safe untouched copies of all issued versions and was able to just swap in a god copy.

No idea what happened to the original, but keep plenty of good backups!

 

[Minty]

swap in a god copy.

I like the idea of a god copy - Omnipotent and able to fix itself...

 

[Frothingslosh]

I like the idea of a god copy - Omnipotent and able to fix itself...

Gates only knows that I could use one of those right now....

 

[smig]

I think it has something with the indexes.
When this happen I will try copy the db (Simple Drag&Drop copy), open the copy and Compact and Repair.
My Guess it has something to do with indexes is because the Copied db will be much smaller then trying to Compact and Repair the original one.