Is there any way to cause IIS 4.0 to default to using SQL_DRIVER_NOPROMPT for all ODBC connection strings (not just when a connection string is specified in code)?
The situation is:
IIS 4.0 on one server (Web Server)
Access97 database on another server (Access Database Server)
Sql Server 7 on another server (Sql Server Database Server)
All of the tables in the Access97 database are linked (via ODBC) to tables in the Sql Server 7 database.
IIS 4.0 has no trouble accssing info "native" to the Access97 database (Table names, Field Names, etc.), but when trying to access data in the linked tables an ODBC trace indicates a failure do to using "SQL_DRIVER_COMPLETE_REQUIRED" rather than "SQL_DRIVER_NOPROMPT" in the connection string (sent by IIS 4.0, not configured in code).
The connection string in the asp is:
Provider=Microsoft.Jet.OLEDB.4.0;Data Source=\\eraqceccs\cem\cemdps\cemdps.mdb
This string works fine if the tables are "native" Access97 tables, but an ODBC error is generated if the tables are linked to SQL SERVER tables.
The situation is:
IIS 4.0 on one server (Web Server)
Access97 database on another server (Access Database Server)
Sql Server 7 on another server (Sql Server Database Server)
All of the tables in the Access97 database are linked (via ODBC) to tables in the Sql Server 7 database.
IIS 4.0 has no trouble accssing info "native" to the Access97 database (Table names, Field Names, etc.), but when trying to access data in the linked tables an ODBC trace indicates a failure do to using "SQL_DRIVER_COMPLETE_REQUIRED" rather than "SQL_DRIVER_NOPROMPT" in the connection string (sent by IIS 4.0, not configured in code).
The connection string in the asp is:
Provider=Microsoft.Jet.OLEDB.4.0;Data Source=\\eraqceccs\cem\cemdps\cemdps.mdb
This string works fine if the tables are "native" Access97 tables, but an ODBC error is generated if the tables are linked to SQL SERVER tables.