I'm afraid you will not be able to solve this. We haven't.
The only choice is to use older PC (OS is not important, even on Windows 10 it works fine on older machines). However I can't tell how old machine and which older hardware is necessary.
I will try that also. But somehow I think it is a software bug caused by a Windows update.
I was told by their tech support they are switching to SQL by summer of 2021 because they can't figure out what is wrong. But I need a solution in the meantime to make it work.
It will be interesting to see their way to SQL. I think they are not competent enough to do it smoothly for all users.
As per your problem... You can try following. If you have only one user in a network accessing this big database that is slowing software down, you can install another instance of the software only on his computer and transfer only this big database to it.
This is how I overcome this problem in one location.
- - - Updated - - -
How big is the database that causes problems?
I know what you mean but it is not how most of my users use it. Several of them works on a same database usually. Gigabit network, no network issues, tried with cat6 cables and a separate switch with just 3 users, tried moving the database to different PC-s, always the same. For a brief period, it worked with realtek drivers installed on network cards (fix their support suggested). But something happened after that with Windows updates that made the problem come back. I disabled driver updates trough Windows update but something else must have made it worse. I know it is a software issue but I have no idea how to troubleshoot it or get an idea what is causing it. It’s like the client PC hangs after you click save or waits for an answer from server PC but why it takes so long to get an answer is beyond me.
Total size of the folder for that year is 258mb. Several databases with *.mdb extension. I have tried adding it in exception in ESET and firewall also, but it did not help.
I got your point. In my case also several users use this database, but only 1 had this speed issue. So I moved software to his PC only with this 1 database and then re-mapped other users to this PC, to use this instance of software just for this one database.
I tried all the things you mentioned, nothing helps. I think drivers have nothing to do with it. Tested on several PC's, different network cards, even on Wi-Fi for test - always the same problem.
Usually it starts to slow down after database gets bigger than ~ 100 MB.
Quote