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
sup****t 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 sup****t
Unicode?
