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-03T22:56:06+00:00

    Was this answer helpful?

    0 comments
  2. Anonymous
    2022-02-04T08:08:58+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.

    Thanks nrgins... I am explicitly closing all recordset objects (before setting the variable to Nothing) but I'm not attempting to close the CurrentDB object ( I guess that it wont let me do that!!??)

    As for your second point... I'm not sure that it is a completely separate issue... I am seeing both issues and to my mind... if Access is not closing connections properly it maybe that locks are being left in place too??

    Was this answer helpful?

    0 comments
  3. Anonymous
    2022-02-04T08:10:40+00:00

    Many thanks Daniel

    I've tried the trusted folder solution.. but it doesnt seem to make any difference.... I'm about to try and roll back by Office version

    Thanks again

    Phil

    Was this answer helpful?

    0 comments
  4. Anonymous
    2022-02-04T08:46:57+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.

    Thanks nrgins... I am explicitly closing all recordset objects (before setting the variable to Nothing) but I'm not attempting to close the CurrentDB object ( I guess that it wont let me do that!!??)

    As for your second point... I'm not sure that it is a completely separate issue... I am seeing both issues and to my mind... if Access is not closing connections properly it maybe that locks are being left in place too??

    Yeah, there's some confusion here because I'm replying both to you and to PBallou.

    And, yes, as I wrote in my second message to PBallou that's right. It does seem that it is related to this Access bug. If Access is not closing the databases, then eventually it will hit the limit.

    It seems that applying the Trusted Location solution should work for you. Did you apply it to both the front end and the back end locations? Did you check the box to include subfolders? Seems to fix the problem for everyone else.

    Was this answer helpful?

    0 comments