Tip with CGI and ODBC driver
Posted: Wed Jul 28, 2010 3:42 pm
I have 1 My SQL server and 1 MS SQL server on my local network
-I can access both of them from a RunRev stack or standalone using the MySQL driver for the first and the ODBC driver for the second
-I can access the MySQL server from a RunRev CGI (as described here :
http://forums.runrev.com/phpBB2/viewtop ... 755#p21119
-But I can't access the MS SQL server from a RunRev CGI
Error message : [Microsoft][Gestionnaire de pilotes ODBC] Source de données introuvable et nom de pilote non spécifié
Can't find the datasource.
But the very same datasource works very well with a RunRev stack or a RunRev standalone. So why not with RunRev CGI ?
Eventually I found the cause : my original datasource was a "user datasource". I created a new one, but as "system datasource" and then bingo, it worked with a CGI.
I can't explain why a RunRev stack or standalone is okay with a "user datasource", when a CGI needs a "system datasource" with the ODBC driver.
-I can access both of them from a RunRev stack or standalone using the MySQL driver for the first and the ODBC driver for the second
-I can access the MySQL server from a RunRev CGI (as described here :
http://forums.runrev.com/phpBB2/viewtop ... 755#p21119
-But I can't access the MS SQL server from a RunRev CGI
Error message : [Microsoft][Gestionnaire de pilotes ODBC] Source de données introuvable et nom de pilote non spécifié
Can't find the datasource.
But the very same datasource works very well with a RunRev stack or a RunRev standalone. So why not with RunRev CGI ?
Eventually I found the cause : my original datasource was a "user datasource". I created a new one, but as "system datasource" and then bingo, it worked with a CGI.
I can't explain why a RunRev stack or standalone is okay with a "user datasource", when a CGI needs a "system datasource" with the ODBC driver.