NO, the issue is that native VB6 only uses API interfaces that are limited to ANSI.
The underlaying database is MS Access, which natively supports Unicode, so I assume that the interfaces within VB are where they are limited to ANSI. Yes, there are methods to use Unicode with VB but that seems not to be used within Legacy, and they would need to develop an Unicode version of API to Access. Regards Chris >From my Motorola G6+ On Tue, 26 Nov 2019, 20:28 John Cardinal, <[email protected]> wrote: > 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 > [email protected] > To manage your subscription and unsubscribe > http://legacyusers.com/mailman/listinfo/legacyusergroup_legacyusers.com > Archives at: > http://www.mail-archive.com/[email protected]/ >
-- LegacyUserGroup mailing list [email protected] To manage your subscription and unsubscribe http://legacyusers.com/mailman/listinfo/legacyusergroup_legacyusers.com Archives at: http://www.mail-archive.com/[email protected]/
