Access version 2201 problem with laccdb

Anonymous
2022-01-31T10:47:34+00:00

Hi!

I have a problem when closing Access program since Access version 2201 (26th January 2022).

There is still a "record-locking informations" laccdb not closing (and that results in several other errors as well like accdb is not opening again and others.

I had to go back to version 2112 ... and then all is fine again.

Is this a wellknown problem with version 2201 already? .... and will this be fixed in a next version?

Thanks for answers

G.

Microsoft 365 and Office | Access | For business | Windows

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments
Answer accepted by question author
Anonymous
2022-02-03T13:08:26+00:00

Most valuable professional. It just means MS recognizes that an individual as contributing to the community. Basically, I help in forums a lot, answer lots of questions, have a very extensive website with lots of information... try to help other users freely. I do not work for MS! I am not paid by MS! I simply try to help fellow users when I can.

Was this answer helpful?

3 people found this answer helpful.
0 comments

49 additional answers

Sort by: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2022-02-04T11:37:06+00:00

    I had a similar problem after updating to Office 2108 14326.20738. When trying to close Access it would close the form and appear to be closing but then immediately re-open. It could only be closed by ending the process in Task Manager. The application is split into software in an Access front end linked to an Access or SQL backend. The application also uses two accdes as libraries holding further software. The only fix I found was to combine both the libraries into one accde. Access no longer seems able to handle the two library accdes. We had previously used this configuration for many years.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2022-02-05T04:51:15+00:00

    Thanks for working this out, Dan. Setting a Trusted Location for the file worked. Have to say I hate it when Microsoft breaks things that worked though!

    Paul Overway

    Microsoft Access MVP 2002

    Was this answer helpful?

    0 comments
  3. Anonymous
    2022-02-05T05:00:52+00:00

    I saw that when I at last had the option to leave the debugger and quit my application and quit admittance that a lock document was as yet present which I was unable to erase, Task Manager showed a phantom MSAccess process running. I can kill the cycle, erase the lock record yet they are simply left again next time I run admittance.

    Any strings you're taking part in the Microsoft Answers Community will in any case be in the Office discussion for you to view and answer to, yet they'll presently not be assembled under this point.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2022-02-05T09:37:15+00:00

    Yeah exact same problem here. latest update made the database unusable. Rolled back to an update from December and everything is working again

    Was this answer helpful?

    0 comments