Share via

Opening large Access databases is taking 60 seconds or more to load since recent 365 update.

Anonymous
2024-09-12T18:01:31+00:00

Since Sept 9th, loading a large Access database (50 meg or so) is taking a long time to open. (over 60 seconds) This is even with holding down the shift key to prevent any code from running or effecting the load time. Prior to the 9th, the load time was about 2 or 3 seconds. My version is Access® for Microsoft 365 MSO (Version 2408 Build 16.0.17928.20114) 64-bit. I have already tried restoring an earlier version, but the problem persists. Any advice would be greatly appreciated.

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 No comments

3 answers

Sort by: Most helpful
  1. Anonymous
    2024-09-17T16:35:23+00:00

    Hi,

    Please always state the version and build number from the File - Account page, NOT the one from the About Access dialog.

    1. Do you see build number 17928.20156 on the Account page?
    2. If yes: Have you tried whether the problem goes away when you revert to an older build of Office?

    An interesting test would be version 2406 build 17726.20126 because it included a fix for a potentially related problem.

    1. What is your Windows version and build?

    Servus
    Karl
    ****************
    Access Forever News DevCon
    Access-Entwickler-Konferenz AEK - 19./20.10. Nürnberg

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  2. Anonymous
    2024-09-12T21:56:22+00:00

    Unfortunately, the update did not solve the issue for me. I have even uninstalled office 365 and reinstalled it with all available updates. Nothing seems to work.

    Was this answer helpful?

    0 comments No comments
  3. George Hepworth 22,855 Reputation points Volunteer Moderator
    2024-09-12T18:20:37+00:00

    A known bug, documented here, can cause this. The fix was released on Tuesday of this week as described in our article.

    Was this answer helpful?

    0 comments No comments