Hi Phil
Yes this is a big pain. We thought we would use Unicode but ran into
issues storing data into a non Unicode application. Are you saying your
database is Unicode but your controls are not? I didn't think this was
an option.
Rob Martin
Software Engineer
phone +64 03 377 0495
fax +64 03 377 0496
web www.chreos.com
Wild Software Ltd
Phil Scadden wrote:
I have found non-English software a major pain. If you work with
charsets instead of Unicode, then various bits of software (eg MS
Access) convert to unicode. Charpage issues are pain and similarly there
have been hassles with MS updates on left-right right-left issues. I
have persisted with unicode for all text data passed around by the
application (eg going into database or passed to other programs) but
normal tools for GUI components. Unicode is at less at mercy of what
bizarre setting a user may have done for charset.
_______________________________________________
NZ Borland Developers Group - Delphi mailing list
Post: [email protected]
Admin: http://delphi.org.nz/mailman/listinfo/delphi
Unsubscribe: send an email to [EMAIL PROTECTED] with Subject: unsubscribe
