Jurand wrote:
The same problem occurs if OTLP database is choosen. After few tests it starts works - maybe data in application is correctly initialized.It means that the database supports unicode. Table and column names will be in unicode, and you can create unicode character columns if you want. Either by specifying DEFAULT_CODE as UNICODE or by supplying the UNICODE attribute when issuing the CREATE TABLE.
And - does really _Unicode = YES means that databese is unicode
If you don't specify _UNICODE as true, then no unicode-related features will work, and table and column names will be standard ASCII (7-bit I think).
_______________________________________________
sapdb.general mailing list
[EMAIL PROTECTED]
http://listserv.sap.com/mailman/listinfo/sapdb.general
