To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=102623
------- Additional comments from lu...@openoffice.org Wed Mar 10 17:18:35 +0000 2010 ------- I had a further look into this. Part of the problem is the windows ODBC manager. All drivers tested support wide character ODBC function calls (SQLExecuteW, etc) and the single byte character ones (SQLExecute, etc). The windows driver manager sits between OOO and the driver. OOO uses the single byte version of the ODBC function calls and the windows driver manager translates the single byte function calls to wide character ones. It translates also the parameters from system to utf16 in doing so (é in UTF8 is two bytes, translating with system to utf16 gives two wide characters). The drivers continue with the utf16 values and will use wrong field names. This explains the first 2 errors reported in the original issue. I have to conclude that this is not an OOO issue. The test case in my earlier comment today does however still show a problem with a double translation in OOO. --------------------------------------------------------------------- Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@dba.openoffice.org For additional commands, e-mail: issues-h...@dba.openoffice.org
