Hi Shubham,

AFAIK:

$sys_charset is related to Uniface versus operating system. Example: defining $sys_charset = UTF8 all your filedump will be saved as UTF-8 character set.

$def_charset is related to Uniface versus (R)DBMS layer. Example: defining $def_charset = UTF8 all your string fields defined with C interface will be saved as UTF-8 character set if the related (R)DBMS is supporting it.

Hope it helps.

Gianni

Hi Gianni,

Thank you for responding.

I would like to modify my question. Actually when the application was working with Uniface 97, we had [SETTINGS] as $sys_charset = UTF8 and all characters in the application used to be display perfectly. But after migrating to Uniface 10, [SETTINGS] $sys_charset= UTF8 does not work good, after replacing it with $def_charsec = UTF8 and now every character in the application is displayed as it should.. Can you help me understand this, why we face such behavior?

One difference i would like to bring in your notice is previously we use to have oracle driver version 12.1.0.2 (for Uniface 97), but now we have oracle 19.3.0.0 does this make any difference?

Thanks $ Regards

------------------------------
Shubham Saini
Uniface Community Edition Shared Account
US
------------------------------

Hi Shubham,

(R)DBMSs, but also all other layers  in the software stack, are moving in the direction to have a whatever UTF-x as base character set, being it an universal base ground. I am not anymore an Oracle expert but I suppose the change you were forced to was generated from different defaults into Oracle configurations of your two installations (version 12 vs. version 19).

The Oracle Uniface driver AFAIK has not changed its functionalities during latest Uniface versions; it was just re-compiled and re-tested to use libraries from newest Oracle versions.

Regards,
Gianni