NOTICE: Our Community is moving. Get more information.
Why does a Visual Basic 6 CaliberRM SDK application not handle unicode characters?
This is not a problem with CaliberRM, as CaliberRM is a unicode
enabled application. This is a Visual Basic 6 issue.
Visual Basic 6 internally stores strings in ANSI format therefore
any character above ANSI code 255 will not be stored correctly
internally. This results in errors when writing strings to files.
There are two workarounds to this problem:
This second workaround will not display the correct character
but will stop the error occuring.
The following characters are displayed correctly in the CaliberRM
But when read into a Visual Basic application, Visual Basic
6 cannot covert the âˆ› to an
Using the StrConv(MyString,vbUnicode,2057) function will allow the
application to handle the character without error, but the
character will be displayed incorrectly as