BUG: In-line Comments Parsed by Microsoft Oracle Driver

• Microsoft ODBC for Oracle, version 2.0 (Build 2.73.7269)

SYMPTOMS

When using in-line comments the Microsoft ODBC for Oracle driver may fail with the following error message:

   "Syntax Error or Access Violation".

CAUSE

The driver is incorrectly parsing in-line comments. So far, the word "IS" is the only word that has caused the error to occur.

RESOLUTION

There is no work around to this problem. You cannot use in-line comments that contain the word "IS" using the currently released version of the driver.

NOTE: Version 1.0 of the Microsoft Oracle driver did not have this problem.

STATUS

Microsoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article. We are researching this bug and will post new information here in the Microsoft Knowledge Base as it becomes available.

MORE INFORMATION

In-line comments can be used to send optimizer hints to the Oracle database engine.

Steps to Reproduce Behavior

Using ODBCTest the problem can be reproduced.

1. Open a Full Connection.

2. Enter the following SQL:

         select empno, ename from emp
         where /* This is a comment */
         empno = 7369
   

   NOTE: You may need to change the code above to reference a table in your schema.

3. Execute the code.

   The following error message is received:

         SQLExecDirect:
         In:hstmt = 0x00301250, szSqlStr = "select empno, ename from emp
         where /* This is a comme...", cbSqlStr = -3 Return:   SQL_ERROR=-1
         stmt:szSqlState = "42000", *pfNativeError = 0, *pcbErrorMsg = 67,
         *ColumnNumber = -2, *RowNumber = -2
         MessageText = "[Microsoft][ODBC driver for Oracle]Syntax error or
         access violation"