So a split Access application, (Access front end and Access backend) presumably all 8 users are accessing the same backend? This is a recipe for disaster.
Access can typically only handle 3 users easily. By 4 users it slows to a crawl. With 8 nothing will move.
Time to upsize to SQL Server Express. And, yes, this is the kinda work I do...and make £££ from it.
-
Access application???
So front end is in access forms?
8 people using it?
How many records?
You need to get them a Cray.
Or look at the locking and advise an upgrade to SQL & web.Leave a comment:
-
Having an 8 core system and running Access on it, is a crime against computer science.Leave a comment:
-
Locks on tables or rather perceived locks on tables will be the cause.
If its a single access backend (and it wouldn't surprise me if it is) then you need to replace that backend with sql server. To be honest the quickest fix would be to migrate the tables to sql server and link the tables back to access.Leave a comment:
-
Access 97 used to have a bit of a bug that would cause this but surely the application isn't that old.
Access in general is a pretty crap product in my opinion. Time to get the application converted to SQL!?!Leave a comment:
-
8 Cores running at 100%
Software house is in clag with their main customer, and they have asked me to advise them, being their only consultant.
It is an ACCESS application, access back end. running 8 times on a box, in different folders
8 users log on via citrix
its an unusual setup - but why would the cpu max out at 100% ?
I have a couple of hours before I have to sit in on a tele conference
tia
EO
Leave a comment: