We've encountered a problem using the UniDAC components.
At first some general information:
- Provider: ODBC
- ODBC driver: Sybase SQL Anywhere 17 (or SAP SQL Anywhere 17 if you prefer)
- UniDAC version: 8.0.1
- Character set encoding: UTF-8
When an exception is raised by a sql statement, it starts to act odd.
The error messages returned by the UniDAC components are empty (an empty string to be exact):
That empty error message problem occurs when the encoding of the database is set to utf-8.
It does not occur when the encoding is set to windows-1252:
The statement executed to generate this error message was 'SELECT 1 FROM x;', whereas the table 'x' doesn't exist.
To narrow down the problem I tried different components to access the database, and all of the components returned the correct error message, even when the database was using utf-8.
Aside from that, the umlauts using utf-8 are incorrect, when an error is returned describing a connection error:
This error message was generated using invalid login data.
The following options were used in the TUniConnection component:
I hope the information provided is helpful to solve this problem.
Kind regards
Pascal Vahlberg
(Developer at COMLAB Computer GmbH)
P.S.: I already filled out the support contact form on your website, but I neither received an answer, nor did I receive the copy I checked to receive.