MarnickTelenet
Programmer
We have a lot of rpt-reports that are made based on an ODBC-connection to SQL2000-server.
We migrated to SQL2005-server an now a lot of reports give the error: "The database table <stored procedure> cannot be found."
It has nothing to do with the version of CR. We have the same problem in CR10 and in CRXI.
We think it has something to do with de ODBC-driver that CR uses to connect to SQL2005. If we reset the ODBC-connection to SQL2000, the report works. As soon as we set the ODBC-connection to SQL2005 the problem is back.
We MUST migrate to SQL2005, but we can't: not because of a problem with our application but because of a problem between Crystal Reports and SQL2005-server.
We migrated to SQL2005-server an now a lot of reports give the error: "The database table <stored procedure> cannot be found."
It has nothing to do with the version of CR. We have the same problem in CR10 and in CRXI.
We think it has something to do with de ODBC-driver that CR uses to connect to SQL2005. If we reset the ODBC-connection to SQL2000, the report works. As soon as we set the ODBC-connection to SQL2005 the problem is back.
We MUST migrate to SQL2005, but we can't: not because of a problem with our application but because of a problem between Crystal Reports and SQL2005-server.