Unfortunately I have never used any flavor of VB, so I'm afraid I'm not going to be much help. However, if I were you, I'd take the code that uses VfpOleDb out of that sample VisData app and try and tweak it to your existing app. Don't change anything else except to use OleDb instead of ODBC. I'm assuming that your existing app works fine except for that one field with the high ASCII values?

Have you played with .NET at all?

~~Bonnie



>I'm so new to VB and databases that I don't really know how to do that. I have seen that it is possible to do in VB since it has been done in VisData, a sample VB app that came with my copy of Visual Studio 6. I am trying to see how it does things. There are so many methods of accessing data it is a bit confusing. I don't know whether to use DAO, ADO, ODBC, etc. I don't know which may be a subset of another.
>
>Larry
>
>>Larry,
>>
>>It's been awhile since I've done anything with VFP (and never with any form of VB) ... so I have no answers, just suggestions ... perhaps the VFPOleDb driver will work better. Have you given it a try?
>>
>>~~Bonnie
>>
>>
>>
>>>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.