FIX: Access Violation with SQLConfigDatasource & Oracle DriverLast reviewed: February 12, 1998Article ID: Q180840 |
The information in this article applies to:
SYMPTOMSWhen you attempt to create an ODBC data source with the SQLConfigDatasource API and the Microsoft ODBC Driver for Oracle version 1.0 (Msorcl10.dll), you get one of error messages listed below. On Windows 95:
<APPLICATION.EXE> has caused an invalid page fault in module MSORCL10.DLL at 0137:61016bae.On Windows NT 4.0:
The instruction at "0x61016bae" referenced memory at "0x00000000". The memory could not be "read". CAUSEThis is a known bug in the Microsoft ODBC Driver for Oracle, version 1.0. SQLConfigDatasource fails when provided with any invalid attribute string name/value pair.
RESOLUTIONUse only the proper ODBC data source attribute string values found in the Microsoft Knowledge Base article listed in the REFERENCES section or get the updated Oracle ODBC driver version 2.0 that ignores invalid attribute strings.
STATUSMicrosoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article. This bug has been corrected in the Microsoft ODBC for Oracle driver, version 2.0.
MORE INFORMATION
Steps to Reproduce BehaviorRun the following sample code to reproduce the error:
// START OF SAMPLE CODE #include <windows.h> #include <odbcinst.h> #include <stdio.h> void main() { SQLConfigDataSource( NULL, ODBC_ADD_DSN, "Microsoft ODBC Driver for Oracle", "DSN=MSORCL10_DSN\0" // This is valid. "BOGUS=Yada-Yada-Yada\0" // This is invalid. ); } // END OF SAMPLE CODE REFERENCESFor additional information, please see the following article in the Microsoft Knowledge Base:
ARTICLE-ID: Q179236 TITLE : INFO: Using SQLConfigDatasource with MS Oracle ODBC Driver |
Additional query words: kbOracle kbDriver kbODBC
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |