Forum Discussion
Access doesn't close properly. A remaining background process can only be terminated in task manager
- Yes, here also the update available (Europe). Tested en fix the problem. Trusted Location not necessary any more. But I highly recommend it. Otherwise you will have problem starting from April. MS is blocking marcos. Check https://techcommunity.microsoft.com/t5/microsoft-365-blog/helping-users-stay-safe-blocking-internet-macros-by-default-in/ba-p/3071805
I have experienced the same problem. When I terminate the running process and open the database from within the Access interface then the program opens and when I close it the running process terminates. However, when I try to double click on the database file in windows explorer the database does not open. I can at that point still open the database from within Access but then when I close the database the process remains running the the record locking file remains open. If I then terminate the task manager process and again open and close the database from within Access, the record locking file closes.
George_Hepworth The only and final solution is a button and docmd.quit acsaveall.
- I'm glad to hear that works in that situation. Unfortunately, it is not generalizable.
George_Hepworth and everyone.
I really need help! I have a 25+ year old Access database that has been running just fine, and continues to run just fine on older computers, and still works fine after upgrading to the 64 bit, latest version.
Even back then, I set it up with a main program MDB (now acddb), and linked tables to a separate accdb file. The program uses extensive VBA code- more than 750k lines of code! - and everything has been working just fine until this Spring.
Any new customer who has installed it has the same issue reported here. You can open it once, but then when it closes, it's 'locked' and the only way to bring it back is to reboot the computer or kill the MSACCESS.EXE process.
I have updated to the latest version 17531.20120, added the directory to the Trust center, and allowed / disabled all warnings about Active X and other 'malicious' code which I do have as the program generates fixed length file reports, and then deletes "Kill command". While I have always had an "Exit/Quit" button that runs "DoCmd.Quit", I am going to test "DoCmd.Quit acQuitSaveAll"
Question- can someone let me know the definite version where everything used to work? And what's really weird is that on my dev laptop (MS Surface Pro 9), *all* of my previous customers, *and* my wife's laptop, everything works perfectly. But on these two latest installs, same **bleep** 'zombie' process happens.
Any and all help greatly appreciated and if you solve my problem, likely rewarded, lol. 🙂
TIA!
-Jon
ps - This is software for scheduling kids at summer camps, so if there are any summer camp guys here who feel sorry, help a fellow camp guy out! 😉
pss - The only thing- so far- that these two installs have in common is how the hard drive is partitioned. That is, they have a C:\ drive, but it's only for the operating system. Since I place the two Access files on their desktop, I did notice that the actual folder location is something like "C:\users\MS - One Drive\desktop\Camp Scheduling Pro" Where as on mine, it's actually on the C:\ drive itself?
