Well, Forms 2.0 will crash on non-DBCS machines when you try to type in DBCS
data via the IME. Makes them a lot less interesting to use (even though you
can use the latest Office version to correct this problem).
--
MichKa
the only book on internationalization in VB at
http://www.i18nWithVB.com/
Quote:
> I have done a lot of tests on this feature and found a Knowledge Base
> on MSDN that said all standard controls (default set) in VB is ANSI, they
> can not
> display DBCS . We can use MS Form 2.0 controls to display DBCS
> and unicode.
> For example, if you want to show japanese characters in your
> appl developed with VB, you must use a japanese OS version
> (Win2K in my test). Otherwise, you can use some 3rd party controls
> like SmartIU control, Videosoft FlexGrid (unicode) with japanese fonts
> installed on the machine.
> Hope this help
> > Simple question:
> > Is it possible to write a VB appln that all controls work with Unicode
> using
> > WIN2K?
> > Therefore, the appln can be independent of the codepage of the Windows,
> > assuming the required language files are installed. It is similar to
the
> > Unicode web page that can be displayed correctly regardless of the
> language
> > of the Windows.
> > For example, if I build appln for Asian country, the control text output
> and
> > input use the ANSI binary bytes that match with the OS codepage so that
> the
> > correct font can be displayed. That is, the appln must install on OS
with
> > exactly matched language.
> > Any suggestions?
> > Thks
> > James
VB unicode?