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-03T19:40:48+00:00

    Hi,

    My client, who uses this database, has the EXACT SAME Access version and build. And the EXACT SAME accdb file is on their system. Yet when I connect to their system and perform the exact same steps, the error does not occur!

    There have been several reports that putting the database in a Trusted Folder would help against the problems. Could that be the difference between your system and the client's?

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments
  2. Anonymous
    2022-02-03T19:50:54+00:00

    I would 1) see the trusted folder comment elsewhere in this thread, then if that doesn't work 2) roll back as described in elsewhere in this thread and in any case use the Feedback option ( it is in office 365 at least ) to let Microsoft know they've broken you code.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2022-02-03T20:07:19+00:00

    Thank you. Going into Access options, then Office 365 trust settings and adding folders ( I added the local folder that holds the front end, and then checked the allow network folders and added a network folder where our back end data is ) has fixed our problem!

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments
  4. Anonymous
    2022-02-03T22:17:54+00:00

    Thank you. Going into Access options, then Office 365 trust settings and adding folders ( I added the local folder that holds the front end, and then checked the allow network folders and added a network folder where our back end data is ) has fixed our problem!

    Thank you! That fixed the problem for me too!

    Was this answer helpful?

    0 comments