Having several Access Apps I've written, I start and exit them a lot. Some are .mdb, some .accdb. I've noticed that when I close an App, sometimes an MSACCESS.EXE process remains running. I can't use it for anything, it just sits there, and ends up reopening after any Windows 10 restarts. How do I stop this, that is, make sure the process ends when I close an App?
Kevin Yip
@Reply 2 years ago
You have to go to the Windows Task Manager and end its process. This can happen to any Windows applications, so you can't really prevent this once and for all. Usually it happens when the application crashes and can't "clean up after itself," so it stays in the memory Crashes can sometimes happen silently too, so you may not realize it until you can't start the application and notice that it is still in the task manager.
I've noticed that if Access isn't behaving itself, it's usually because something in your coding wasn't done right. Like maybe you're declaring object variables and not destroying them when you're done, or you've got an endless loop running somewhere in the background. Of course, never blame the application, right? It's always the programmer! LOL
Donald ShroyerOP
@Reply
2 years ago
All of my applications have been used and running without this issue for many years, some for decades. An App error is certainly possible, but not lkely. It feels to me more like a Win10 update issue, which I thought you folks might be able to confirm or deny. Posts about this elsewhere indicate the presence of any Forms with VBA code will result, but I've not been able to confirm that. Further, sometimes the apps will close normally, and sometimes not.
Have I seen poorly programmed databases not close properly and keep MSAccess.EXE running in the background? Yes, sure, and I'm responsible for some of those bad programming jobs. LOL! But it's not a known bug that I'm aware of that affects just average everyday small databases.
Donald ShroyerOP
@Reply
2 years ago
As I've tried to point out, this behavior has ONLY BEGUN RECENTLY. Is there something about recent Access or Win10 updates that could account for this?
You can check the Windows event logs for any application errors related to Access, but not all errors are recorded there. Also, if you use multiple PCs, and these problems occur only on that one PC, you need to isolate that PC for investigation. If the problem only occurs to specific .accdb files but not others, you need to isolate them too.
Sorry, only students may add comments.
Click here for more
information on how you can set up an account.
If you are a Visitor, go ahead and post your reply as a
new comment, and we'll move it here for you
once it's approved. Be sure to use the same name and email address.
This thread is now CLOSED. If you wish to comment, start a NEW discussion in
Visitor Forum.
