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

    Was this answer helpful?

    0 comments
  2. Anonymous
    2022-02-03T22:53:04+00:00

    Thanks.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2022-02-03T22:45:43+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?

    Yeah, you can't close CurrentDB, since it's, well, the current db. ;-)

    The code you were running was fine. Seems that the Access bug did cause your code to fail at 255 iterations. I've done what you did many times, going past 255 iterations, and there's no problem usually.

    But it seems that applying the Trusted Locations workaround resolved the problem for you. So that's great!

    One thing I'll note: you should always use dbFailOnError when using the execute method, so that you'll know if there's an error, i,.e.:

    CurrentDB.Execute sqlstring, dbFailOnError

    Was this answer helpful?

    0 comments
  4. Anonymous
    2022-02-03T22:20:14+00:00

    Daniel … I didn‘t know … I thought you‘re a Microsoft agent - sorry.

    Thank you for all your help here - great 👍🏼

    Was this answer helpful?

    0 comments