Problems on Unicode-DBs after updating to DOA 4.1

[lecare039]

Hello.

Until now I developed with DOA 4.0.7.

We recommered our customers to run an ASCII-DB, but none the less at least one customer was (and is) running a unicode-db so the charset is set to be AL32UTF8.
Never the less, the Client was/is running on a german Windows and the charset is set to WE8MSWIN1252, corresponding to the Windows Codepage.

After updating to DOA 4.1 problems appear.

Until now - developing the program with DOA 4.0.7 - there where no problems with german umlauts (like

 

[Marco Kalter]

If you do not want to fetch Unicode data from your Unicode databases, you can set Oracle.NoUnicodeSupport to True at run-time.

 

[lecare039]

Thx, this seems to work as expected.

But one more question. Is this variable only interpreted while running on an unicode-db or does it also has an affect on nonunicode-dbs?

Maybe you should expand your helpfile? Even though you search for "NoUnicodeSupport" you won't find anythink.

mfg

 

[Marco Kalter]

It does not have any effect on a non-Unicode database.

And you are right, it is missing from the documentation. We'll add it.