Chris,
It's easy to support 16-bit Unicode characters in VB6. There are a few places where a program has to be careful to use the "W" version of a Windows API call (not the "A" version), but that's a well-understood issue and unlikely to be a significant problem. The 16-bit subset of Unicode covers every character anyone reading this message cares about, but is not the full set of Unicode characters. So, if VB6 is not the issue, what is? My guess is that the database layer in Legacy uses FoxPro or some other database component that uses 8-bit characters and the old Windows "code page" approach to character encoding. If so, that's where the limitation lies. John
-- LegacyUserGroup mailing list LegacyUserGroup@legacyusers.com To manage your subscription and unsubscribe http://legacyusers.com/mailman/listinfo/legacyusergroup_legacyusers.com Archives at: http://www.mail-archive.com/legacyusergroup@legacyusers.com/
