Why are you using the dBase III ODBC driver instead of the VFP ODBC driver or even better, the VFP OLEDB Provider?

>We have a VB6 program that is trying to take data from a DBF file and load it into a SQL Server table. There is a CHAR(4) field that contains characters that have an ASCII value > 128. When the VB6 program accesses this field via the dBASE III ODBC connector it translates the high order characters to some other high order value. For example, the character whose ASCII value was 138 comes back as 232.
>
>I don't know if this is a VB thing or an ODBC thing. Is it possible to work around this in VB6 (or VB.Net or C#)? I know VFP6 can handle reading the field properly but I'd like to avoid redeveloping this app. But, if it has to, it has to.
>
>Thanks in advance for any advice/help.