Unexpected closure

[Gismo]

Hi all,

My one DB will just close unexpectedly without warning and a backup opens

How do I trouble shoot the reason for this?
I do my compact and repair often as well as debug

 

[theDBguy]

Have you tried importing all your objects into a new database?

 

[Gismo]

Have you tried importing all your objects into a new database?

Hi,

yes I did that, quite a while ago, still had the same issue
I noticed that when it closed, the response was very slow in opening any form

 

[isladogs]

Have you tried decompiling your project? That removes possible corruption in compile code. See Decompile and Compact Your Microsoft Access Database to Improve Performance and Fix Corruption (fmsinc.com)

 

[Gismo]

Have you tried decompiling your project? That removes possible corruption in compile code. See Decompile and Compact Your Microsoft Access Database to Improve Performance and Fix Corruption (fmsinc.com)

Hi,

I have compiled a few times as well

 

[isladogs]

That's not what I'm suggesting. Please read the article.

 

[RogerCooper]

Trying repairing your installation of Access.

 

[Isaac]

But Pat it does usually give that ugly "execution of this application can't continue and will be shut down" error. (doesn't it? it's been too long since I had untrapped runtime errors for me to know, but it used to). I haven't seen it shut down just silently (at least, not due to that scenario - untrapped error in runtime). In that case, as Chevelle says, "Closure will come"

 

[The_Doc_Man]

There are two ways to look at this, not necessarily mutually exclusive.

Either you can add code to report an error OR you can check the event viewer to see if Access reports an error in the system error logs. As "must shut down" class of error USUALLY does that.

 

[Isaac]

I want to add some thoughts due to things I have seen (in person at my jobs) of people doing that are totally outside the bounds of what VBA and Access (or even Excel) expect, and can cause ALL kinds of corruption issues.

- Failure to follow this simple sequence, ALL the time:

1. Do some development/design work
2. Debug > Compile
3. Save
4. Use the application

- Failure to follow this simple sequence all the time:

1. You're in break mode - do not edit any code!
2. Get out of break mode (by pressing Stop, or passing an Exit)
3. Proceed.

Not following those sequences can just bring the VBA project into a state of total chaos IMHO.

I've seen people who are over a year into VBA development/learning and they are still trying to do things like editing code in break mode or fully deploying and utilizing totally uncompiled applications. In my experience, doing either of those is asking for trouble. The latter there may be some special circumstances that may warrant, but I haven't come across them yet.

 

[Gismo]

That's not what I'm suggesting. Please read the article.

Hi,

yes I did read the article