We have a VB.NET application (VS 2005) that produces reports created with Crystal 2008. This application has been running nicely for over a year running against SQL 2005 / SQL 2005 Express.
Reports are data-sourced to SQL stored procedures, and we access them through the SQL native client which is distributed with any install copy. As said, things have been running well for a long time.
However, this week one of our QA guys started testing our app against SQL 2008 and we found that not a single report runs. On every one of them we get the error "Logon Failed, Unable to connect: incorrect log on parameters". Note WE HAVE CHANGED NO CODE AT ALL - its the same app, just running against SQL 2008 instead of SQL 2005.
Can anyone explain to me what is happening? It is presumptive that this is a SQL 2008 glitch, but has Crystal done anything to test or address running against SQL 2008?
Any help is great appreciated!