I suspect what you describe as a funny character is a Unicode identifier -
so problems converting from one character set into another, I suspect. You
may need to set your LCID and/or charsets to handle unicode data (if indeed
this is the problem)

Signature
Jason Brown
Microsoft GTSC, IIS
This posting is provided "AS IS" with no warranties, and confers no
rights.
> Hi,
>
[quoted text clipped - 38 lines]
> objConnection.Close()
> End Sub
Jullietta - 26 Oct 2004 00:15 GMT
Thanx Jason, all I had to do was change a line in the schema file to
handle unicode characters!!
If anyone else has this problem here is the schema.ini file that
solved my problem.
Cheers
Jules
[CSV.txt]
ColNameHeader=False
Format=CSVDelimited
MaxScanRows=0
CharacterSet=UNICODE
Col1=RecordType Char Width 200
Col2=DateAndTime Char Width 200
Col3=AO Char Width 200
Col4=Object Char Width 200
Col5=asd Char Width 200
Col6=dfg Char Width 200