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: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2022-02-07T02:21:25+00:00

    I've found that running some VBA code is enough to cause the problem. I created a new database with no tables and a single form with one unbound textbox control. This would open and quit without leaving Access still running as a process. Then I added a single line of code in the form's Open event to set the form's caption to a simple string (Me.Caption = "whatever"). Now Access won't quit properly.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  2. Anonymous
    2022-02-07T00:01:58+00:00

    Hi Daniel,

    Thanks so much; the trust center settings workaround did the trick:

    File-->options-->Trust Center--> Trust Center Settings --> Trusted Locations -->Add a new location

    thanks again !

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  3. Anonymous
    2022-02-03T22:19:35+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?

    Hi, Karl. Yes, that was it! I checked on the client's system, and they already had the front end and back end locations set as "Trusted Locations". That's apparently why they weren't affected.

    And, as I just noted to PB, setting my development folder to be a Trusted Location fixed the problem for me as well!

    Thanks!

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  4. Anonymous
    2022-02-03T16:35:31+00:00

    Ive had a very similar problem since about the 10th January on a database which has worked without problem for at least 6 months... ive done a little investigate (running a recursive loop to see how many db objects can be opened before hitting the no more databases error) and it seems that (in some cases) the database connection entry doesn't get release by set <db/recordset object> = null. I use myDB.Execute or CurrentDB.Execute and if you switch to DoCMD.RunSQL the problem doesnt occur.

    I also started getting the the database is in use by use <admin>

    Phil

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments