Reading text files with UTF-8 byte order mark

I have a simple VBA application that reads text files using an ADO 2.x
library. The application that creates the text file has been "enhanced" to
support Unicode, and now places a UTF-8 byte order mark (BOM) as the first
three characters of the file ... , hex values EF BB BF. ADO 2.x doesn't
seem to "speak" Unicode, and doesn't interpret these characters as a BOM.
Instead, the three characters are include in the first row, first field value
.... a field name in my case.

All I can find is an ANSI versus OEM setting in the schema.ini file. Am I
missing something, or does ADO 2.x reading text files simply not support
Unicode?
.

Relevant Pages

  • Re: Unicode Support
    ... > compiler/assembler is unicode support. ... > but the fact that most assemblers, ... Most popular *editing* tools support this data format. ... Is there really a need to put unicode characters into identifiers? ...
    (alt.lang.asm)
  • Unicode text editor mined 2000 release 11
    ... Mined provides both extensive Unicode and CJK support offering many ... of terminal variations, or Han character information). ... It was the first editor that supported Unicode in a plain-text terminal. ...
    (comp.os.linux.announce)
  • Re: Unicode-based FreeBSD
    ... displaying specialised characters on the screen/tty. ... There are special Input Methods for the rest of Unicode. ... Unicode support and the FreeBSD developers see little reason to ...
    (freebsd-current)
  • Unicode text editor mined 2000 release 11
    ... are not aware of (like auto-detection features and automatic handling ... It was the first editor that supported Unicode in a plain-text terminal. ... Combining character width properties. ... Added keyboard configuration examples for Control-function key detection for rxvt and mlterm to the runtime support library. ...
    (comp.editors)
  • Re: Unicode Support
    ... >> compiler/assembler is unicode support. ... >> but the fact that most assemblers, ... Most popular *editing* tools support this data ... > Is there really a need to put unicode characters into identifiers? ...
    (alt.lang.asm)
Loading