2) Change SQLColumns, SQLTablePrivileges to take show_system_tables<br>\r
option into account.<br>\r
3) When an ODBC 2.x application working with an ODBC 3.x driver<br>\r
-\81B\81v\81Eòcalls SQLExecDirect, SQLExecute, or SQLParamData, and a searched<br>\r
-\81B\81v\81Eòupdate or delete statement was executed but did not affect any<br>\r
-\81B\81v\81Eòrows at the data source, the ODBC 3.x driver should return<br>\r
-\81B\81v\81EòSQL_SUCCESS. When an ODBC 3.x application working with an ODBC<br>\r
-\81B\81v\81E\81E.x driver calls SQLExecDirect, SQLExecute, or SQLParamData<br>\r
-\81B\81v\81Eòwith the same result, the ODBC 3.x driver should return SQL_NO_DATA. <br>\r
+1.calls SQLExecDirect, SQLExecute, or SQLParamData, and a searched<br>\r
+2.update or delete statement was executed but did not affect any<br>\r
+3.rows at the data source, the ODBC 3.x driver should return<br>\r
+4.SQL_SUCCESS. When an ODBC 3.x application working with an ODBC<br>\r
+5.3.x driver calls SQLExecDirect, SQLExecute, or SQLParamData<br>\r
+6.with the same result, the ODBC 3.x driver should return SQL_NO_DATA.<br>\r
<br>\r
1.29 by hinoue <br>\r
Mon Nov 10 02:10:07 2003 (10 hours, 1 minute ago)<br>\r