IBDac not displaying certain chars from Unicode_FSS db

upscene · Post by **upscene** » Thu 06 May 2010 13:54

Hi,

UseUnicode is True.

I have here a certain test database from a customer, it was created with char set UNICODE_FSS and manipulated with IBObjects.

My own IBO application displays the characters just fine, now when using IBDac, setting UseUnicode to True, the non ASCII characters aren't displayed.

Can I send this database somewhere?

With regards,

Martijn Tonies
Upscene Productions

Dimon · Post by **Dimon** » Tue 11 May 2010 07:17

To solve the problem try to set the UseUnicode option to False and the TIBCConnection.Options.Charset property to UNICODE_FSS.
If it doesn't solve the problem, please send me your database to dmitryg*devart*com.

upscene · Post by **upscene** » Tue 11 May 2010 07:31

Dimon wrote:To solve the problem try to set the UseUnicode option to False and the TIBCConnection.Options.Charset property to UNICODE_FSS.
If it doesn't solve the problem, please send me your database to dmitryg*devart*com.

I believe I was told that UseUnicode uses UNICODE_FSS always?

What would be the difference between these two?

Dimon · Post by **Dimon** » Tue 11 May 2010 09:33

When UseUnicode is True IBDAC creates WideString fields instead of String fields.

upscene · Post by **upscene** » Tue 11 May 2010 09:45

Dimon wrote:When UseUnicode is True IBDAC creates WideString fields instead of String fields.

Does a string-field make sense for Unicode_FSS charset? This cannot display the special chars properly, right?

Mind you, this is a generic application so it should work for all occasions. Currently, UseUnicode is set to False when the charset is NONE, but for all others, it's set to True.

Dimon · Post by **Dimon** » Wed 12 May 2010 09:54

upscene wrote:Can I send this database somewhere?

Please, send me a small sample to demonstrate the problem and the database to dmitryg*devart*com.