Forum Discussion
Access slow to open
I am also experiencing this issue, wherein if I open the .accdb files it would
take a whole minute or sometimes more than 2 mins! Made me frustrated resulting to
format my PC and started fresh and go through installation hell!
After installing all my essential application for works and tried again opening the .accdb files everything back to normal. So O added android emulator for my gaming pleasure, while gaming with my android emulator... boss called me (wink2) and ask me to check something with the .accdb file and I notice that the SLOW opening of .accdb came back to life again... it took me sometime to notice but when I close my emulator and open the .accdb boom! it fast again.. maybe the memory / cpu cache is drained by the emulator which take a toll with the .accdb cache?
I will try to lessen my emulator cpu usage and will check if it would fix the problem if im using
my emulator and accdb at the same time.
Maybe the case for you is VM?
- papasiloSep 28, 2020Copper ContributorJust a quick update, after change settings with my emulator..
it seems that the cpu usage was the problem, the default settings was using 2 CORES out of 6 Cores (i5 8400). after changing to one and retain the memory usage to 4GB. my emulator is still smooth and my accdb problem is gone. So win win situation 😄- StevenED1964Feb 17, 2022Copper Contributor
I wanted to provide an update on my original post.
Reading through this thread I noted that the original problem for the poster was that he experienced different speeds opening an Access Database depending on the method used to do so.
I tried opening Access first, then opening the database from within Access. The first time around, it did what I expected which was that it closed the current database and opened the second one as the only one.
I then opened a new instance of Access from the Start Bar and opened the second database from the new instance while the first instance still had the first database open. My second database opened immediately.
So for me, the issue is now resolved but it does seem odd that "how you open a database" makes a difference in performance when no other Office product has that same issue. For example, opening multiple Word, Excel, Publisher, or PowerPoint files from Explorer doesn't seem to have a performance hit yet Access seems to experience a very serious performance hit.
Take care.
- papasiloFeb 19, 2022Copper Contributor
StevenED1964
I think this issue that you have experience is from the office update from last week of Jan 2022 or first week of Feb 2022.
Wherein some of the access accdb runs in the background in the first run,it got recently fix update last week.
Hopefully your office got the latest update and fix it 😉Regarding with the emulator that I have a problem before was Bluestacks and I switch to LDPlayer to solve my issue 🙂
- StevenED1964Feb 17, 2022Copper Contributor
What emulator are you using? I occasionally run BlueStacks on my Alienware Area51M laptop but not often.
The problem that I am having is similar but not exactly identical. The issue occurs on my laptop even if I have rebooted and not run BlueStacks at all.
My specific occurrence of this issue is as follows: I open an existing Access Database using Explorer and double-clicking on the database file and the database opens rapidly.However, if I open a subsequent Access Database (using the same method, I have never tried opening from within Access because I thought it would close the already open database) it can take extremely long to open. For instance, I am currently waiting over 26 minutes for the second database to open.
At first, I thought the second database might have gotten corrupted somehow (a common Access "thing") but if I open the second database FIRST, it opens rapidly. The issue doesn't seem to be sp[ecific to any particular database but more of a "first one to be open is fine" and "any subsequent database to be opened is a victim of whatever is going on here. Hmm.
I have not reinstalled Windows on this laptop but I see others have tried that without success anyway. I have reinstalled Office 365 but like the others before me, no success in obtaining a resolution to the issue.