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-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-03T17:08:29+00:00

    You need to close the database objects before setting the object to Nothing (I assume you mean "Nothing" rather than "Null"). Setting the object variable to Nothing releases the variable, but it doesn't actually close the object. You need to first close the object, and then set the variable to Null.

    But you also need to make sure that the object exists before attempting to close it. Otherwise, it'll trigger an error.

    The code I use (for a recordset object called "rs," for example) is this:

    If Not rs Is Nothing Then rs.close

Set rs = Nothing

    That should resolve your problem. And you should be using Execute rather than RunSQL.

    In any case, I think that's a separate issue from what's being discussed in this thread.

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments
  3. Anonymous
    2022-02-03T16:34:33+00:00

    I just want to add to this discussion a strange twist.

    I just started having this problem this morning (Feb. 3). Same symptoms. Get "Could not open any more databases" while using database. When I close Access, a ghost process remains. Have to delete it in Task Manager to be able to reopen Access.

    I found that a simple way to trigger the error is to open my database app and then do a Compact and Repair from the ribbon. That closing and reopening of the file triggers the error. Every time.

    As with others, my Access version is Version 2201 (Build 14827.20158).

    Now, here's the strange twist.

    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!

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments
  4. Anonymous
    2022-02-02T19:25:24+00:00

    Dear Daniel!

    The onliest comment I can see from your side is asking for the build ..... but in reality it's pretty easy:

    All the people with laccdb problems are using version 2201 14827.20158.

    Can you please answer here that Microsoft is aware of the problem and is working on a solution now .... that would help a lot - thank you.

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments