Microsoft Access is not allowing me to compact and repair. Keeps saying its open etc

Anonymous
2022-02-17T10:52:42+00:00

Microsoft Access is not allowing me to compact and repair the database. It keeps saying file is open. I made new database and imported files even then same issue and it says it is opening in sharing mode. I haven't shared with anybody. How to shut off this sharing mode. Mine is a single computer for home and is not part of any network. Please guide. Thank you. Ripal

Microsoft 365 and Office | Access | For home | 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 No comments

60 answers

Sort by: Oldest
  1. Anonymous
    2022-02-27T17:36:58+00:00

    Thanks Daniel for the reply.

    How to do the rollback?

    Also 3 different computers have same build but its working on one and not on the other two. I have a brand new Dell with the newer I7 11390H processor. Here it is not working. On my Lenovo it's an I3 I think 7th Gen and it is working fine on that laptop. On my oldest Dell and I3 3rd gen it's not working.

    From what I have seen today it seems that the I7 11390H struggles and the older i3 7th gen seems to be faster. At least it looked like that to me when I was working on the application.

    To all the technical powerhouses here, please guide, and eat Microsoft's head if necessary to get them to listen. I already gave feedback on the app. Not sure what else to do.

    Ripal

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2022-02-28T15:59:31+00:00

    I've tried reverting to two previous builds, and neither one resolved the problem. Exactly which build would you suggest?

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2022-02-28T16:14:30+00:00

    It depends on your update channel. If you review https://www.devhut.net/access-lock-file-issues/ under the section entitled 'A Little Back History' you'll see the builds that initially caused the issue to first surface, so you need to go to a build prior to those.

    That said, someone else report that even reverting the build doesn't resolve this issue which makes me believe it is a flag controlled by Microsoft that is causing this problem and there is nothing users can do to address it. This is speculation on my part, but the data is pointing that way.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2022-02-28T18:46:16+00:00

    This is all very frustrating.

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2022-02-28T21:30:12+00:00

    Manually checked for updates just minutes ago, and it actually found something. I'm now updated to:

    Microsoft® Access® for Microsoft 365 MSO (Version 2202 Build 16.0.14931.20118) 32-bit

    But the issue persists.

    Was this answer helpful?

    0 comments No comments