Changed DSN in connection object but reports still use value from old DSN
We're running BObj XIr2 SP4 and have both WEBI and DESKI reports. Most of our DESKI reports have two data providers, one from a universe (header/footer info) and one for free-hand SQL (report data). We are testing in preparation to upgrading all our databases to SQL2005 and have created a new DSN which points to a SQL2005 database to be used by our universe and free-hand SQL connections. We modified our existing connections to use the new DSN and to use the SQL2005 database engine. Our WEBI reports are working just fine and are returning data from the SQL2005 database, but on the DESKI reports the header/footer info from the universe is correct but the report data is coming from the "old" SQL2000 server. If we create a new DESKI report and export it, it retrieves data correctly from both data providers, but the existing DESKI reports, which use the same connections, have the same problem. The new DSN exists on the app server and points to the correct database.
We were hoping that, like the WEBI reports, the changes would be transparent to the reports, but that doesn't seem to be working. Is there something we must do to get the existing DESKI reports to recognize and use the new connection parameters?