For the last couple of days, all users have complained of poor system performance.
Background : maximum 6 or 7 users, split FE from BE, persistent connections. C&R on the BE done weekly, usually knocks the BE file size down from about 95MB to about 75MB. FE set to C&R automatically on close. A new FE was released a week ago with no performance hit noticed then but it is poor now, regardless of whether the new or an old FE version is run. I have also C&R'd the BE this morning, but performance is still noticeably poor.
Performance seems poor regardless of how many users are active or what they are doing. As an example a common function is for a user to print a label on their local Dymo printer. Last week the print would start immediately the control was selected, now a message saying "Now printing ..." appears for a significant time (3-4 seconds) before the print starts.
The db will be the main source of network traffic, and IT support claim that nothing has been done to the server or the network which could affect the db.
Showing my ignorance here - does an Access executable run on the server, as if so, would it be worth reinstalling it ? Any ideas what else I could be looking at ?
Background : maximum 6 or 7 users, split FE from BE, persistent connections. C&R on the BE done weekly, usually knocks the BE file size down from about 95MB to about 75MB. FE set to C&R automatically on close. A new FE was released a week ago with no performance hit noticed then but it is poor now, regardless of whether the new or an old FE version is run. I have also C&R'd the BE this morning, but performance is still noticeably poor.
Performance seems poor regardless of how many users are active or what they are doing. As an example a common function is for a user to print a label on their local Dymo printer. Last week the print would start immediately the control was selected, now a message saying "Now printing ..." appears for a significant time (3-4 seconds) before the print starts.
The db will be the main source of network traffic, and IT support claim that nothing has been done to the server or the network which could affect the db.
Showing my ignorance here - does an Access executable run on the server, as if so, would it be worth reinstalling it ? Any ideas what else I could be looking at ?