Hi,

I have a scenario that I'm hoping to see if anyone has come across this. Basically, we wrote an app in VB6 at work. Everything had been tested in regular English Win XP and Vista and confirmed that it's working fine. This app was then installed in Korea, with the Korean version of Windows OS. It was just reported to us that it's not working at all.

Well to make it short, in our code, we have to communicate to a proprietary USB device. The USB communication chip that we purchased retrieves the input buffer from the USB port as a type string. We then depend on the ASC() and Chr() functions in VB 6 a lot to do the parsing of the input buffer. Well, ASC() and Chr() work fine in single byte languages, but we just confirmed that they do not work for double byte asian languages, in this case Korean.

Has any one here come across this problem in the past? The thing that I can't understand is that for example: a character of ASCII code 128, if you run this through the ASC() function, in single byte language systems, it should give you back the value of 128. However, I have noticed that in a double byte language system, it gave me a really strange value of -23834. How can this happen?

If you have any thoughts on this, I really appreciate your help.

Thank you.

Khoi Nguyen

__________________
Khoi Nguyen

The interpretation of numbers sees the most significant byte as the sign. If it is 1, the number is negative. That's how that can happen.

I'm afraid I don't have more to offer on the main question.

Try using ASCW() and CHRW() instead of ASC() and CHR().

I haven't used them with VB6, but they work correctly with VBScript. The "W" is for "W"ide characters--Unicode.

But this may not work at all, depending on how that USB device works. If it can't handle Unicode you may have to do a *LOT* of work, yourself.

Don't you have documentation from the chip manufacturer??