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-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
  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-03T19:09:18+00:00

    THAT'S a handy piece of information right there. Thank you very much. I've been setting my recordsets to nothing, but not closing them. Never ran into an issue until this latest release.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2022-02-03T19:40:04+00:00

    I am using "currentdb.execute sqlstring" to write records to a local table.

    I am looping through data that is read from SQL Server.

    The error described here happens when I have written 247 records to my local db.

    I found that Access has an internal limit of 255 simultaneous connections to Jet.

    I have never used currentdb.close or set currentdb =nothing

    I tried the currentdb.close after each record was written, but the system still bombs at 247 records.

    Any suggestions?

    Was this answer helpful?

    0 comments