Forum Stats

  • 3,770,291 Users
  • 2,253,091 Discussions


OraOLEDB.Oracle vs ODBC, semicolon difference.


I would like to know why the ODBC driver is more than happy to execute queries that terminate with a semicolon while the OraOLEDB driver gives an invalid character error.  If there were an option or something to allow the OraOLEDB to ignore these, then it would make it really, really easy to swap between the two drivers.

BUT, because these two work in slightly different ways, switching away from the buggy ODBC driver is resulting in errors that involve removing a semicolon from the statements in an existing application.

Why does the OraOLEDB driver have to give an error message when a SQL statement is terminated with a semicolon rather than just executing it?  Is there some secret option somewhere I can toggle to make it process the query despite the semicolon?



This discussion has been closed.