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-01-31T10:57:50+00:00

    A version number is not enough information, could you provide your build number, update channel, bitness.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2022-01-31T11:32:29+00:00

    The version who is working now (again) is 2112 14729.20260 (Aktueller Kanal).

    And I'm not pretty sure about the version who was not working .... but I guess it was version 2201 14827.20158 (Aktueller Kanal).

    edit: 32-bit

    edit2: The error occurred first time on 28th of January .... maybe there was also another 2112 version working fine ... I have no idea why my actual version now is lower than the latest 2112 version before updated to 2201

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments
  3. Anonymous
    2022-01-31T20:03:10+00:00

    ... I just read all the threads here from the last few days.

    It seems (luckily??) that I'm not the onliest one having problems with newest 2201 version ... that helps me a lot at the moment .... knowing that's not me doing something wrong.

    I reverted to an earlier version 2112 14729.20260 and it's working fine.

    Is anyone from Microsoft working on that problem?

    Was this answer helpful?

    3 people found this answer helpful.
    0 comments
  4. Anonymous
    2022-02-02T02:52:05+00:00

    Thank you for posting.

    This morning Feb 1, 2022 with MSAccess Office 365 current channel 32 bit Version 2201 Build 16.0.14827.20028 click to run I started getting ""Cannot open any more databases error 3048." on a not too simple but had worked-fine-before form.

    I noticed that when I finally was able to exit the debugger and quit my app and quit access that a lock file was still present which I could not delete, Task Manager showed a ghost MSAccess process running. I can kill the process, delete the lock file but they are just left again next time I run access.

    I changed out a few small read-only subforms to using snapshots instead of dynasets and that seemed to delay the 3048 error messages until I'd scrolled further down the rows in browse mode but I still got the error.

    The ghost process and lock files are still left behind even when I don't browse enough to get a 3048 error. I can open the app without the startup form and close it and then no ghost process or lock file but if I so much as open my startup form when I exit the ghost process and lock file is left behind.

    Was this answer helpful?

    3 people found this answer helpful.
    0 comments