Apologies for such a question...We have a supplier of a piece of software that is made up of an Access front end with a SQL Server back end. It was previously on a Windows 2003 server, with a SQL Server 2005 back end database and it worked fine.It has been moved to Windows 2012 and a SQL Server 2014 database, but still uses Access 2010 runtime. Our users are having terrible performance issues and the supplier is blaming our network. We have carried out extensive tests on the network, servers and database and produced numerous stats proving that there is nothing wrong with any of these elements. The other thing we have discovered is that the application works fine when only one user is in it. More than 1 user and it freezes up, produces many timeout and 'application defined error / object defined error' messages. Therefore, looking at this from a DBA perspective, I feel that perhaps there is a compatibility issue with the newer software, perhaps related to how Access connects to SQL Server (ACE etc). The system was written many years ago and has not been re-written as far as I am aware. Please can anyone advise if you have come across similar issues?Many thanks,Paula
↧
