Our organization is currently transitioning an outdated Access 2000 application that previously connected to a SQL Server 2000 backend to now use a SQL Server 2005 database on a new server. Unfortunately, we’re encountering issues with executing inserts and updates. I’ve come across numerous online discussions indicating that Microsoft does not officially support Access 2000 with SQL Server 2005, but I have yet to locate any formal documentation to confirm this. Could anyone provide a link to official sources or share their experiences regarding this configuration? Additionally, it’s worth noting that the application is an ADP, which has been compiled into an ADE.
Mayb try using an odbc datsource instead of going direct? I had similar issues b4 and switching to odbc helped smooth out some connection probs. Not official, but might work for ur scenario. Also double chec the compatiblity settings on the sql server.
Ever considered checking if there are specific changes needed for your T-SQL statements? Sometimese the differences in SQL versions introduce syntax quirks that need tweaking. Anyone else notice differences in how SQL2005 handles queries compared to SQL2000? Let’s dig deeper into this. 
You can test by running the Access 2000 app in compatibility mode on a more updated Access version. Sometimes, legacy issues get nuanced when switching database engines or versions. Also, check for any potential permissions problems on the new server settings.
In my experience, transitioning from Access 2000 to SQL Server 2005 can indeed present some challenges, particularly due to the lack of direct support for older Access versions with newer SQL Server databases. One approach that helped in our case was upgrading the Access database to a newer version, like Access 2003. This solved many compatibility issues without needing to overhaul the entire system. Additionally, upgrade the ADE file provides better compatibility with SQL Server 2005, helping streamline any SQL queries and updates you might be struggling with.
While upgrading the Access database might be a potential solution, another crucial factor to consider is ensuring that your SQL Server 2005 is configured to allow older legacy applications to connect. Double-check your server settings, especially authentication modes, as SQL Server 2005 might default to Windows Authentication, which could cause connection hiccups if your application requires SQL Server Authentication. You can also explore upgrading your SQL Server Native Client, which often enhances connectivity between older Access versions and newer SQL Server environments, potentially resolving your issues.