Send me the tables, SQL syntax, along with your findings - and I will pass it on to MS.

>The table has SSN, FirstName, and LastName fields. I have an index on SSN as well as LastName. When I query the table by a last name, such as Zimmerman, in the command window, both DOS and VFP return the correct data. However, when I query the same table through ODBC, the Fox 2.x driver returns the Zimmermans, while the VFP driver returns an empty set. I even converted the table to VFP, but still got the same result through VFP ODBC--empty set or incomplete data on queries for last name.
>
>FoxPro driver 3.51.171300 works flawlessly.
>VFP driver 6.00.816700 seems flakely.
>
>I haven't tried to report this to MS. I wanted to see if anyone has had the same experience. The VFP drivers seem much quicker than the older drivers, yet I now question the validity of the result sets...
>
>>What exactly did the VFP ODBC driver return as a result???
>>
>>
>>>As I understand the ODBC docs for the VFP 5 & 6 drivers, you can use those to read Fox 2.x tables. Although the drivers are faster than the Fox 2.x ODBC, they did not return valid results. With a Fox 2.x table of employee data, i.e. SSN and names, the new drivers returned correct results for SSN queries but did not for last name searches. Has anyone experienced similar problems?
>>>
>>>The SSN and Last Name fields are both character. When I searched for last names of Zimmerman, the VFP ODBC returned nothing while Fox 2.x ODBC returned the correct results. However, searching by Mendenhall returned the correct results for both. I had similar problems with Smith and Jones for example--Fox 2.x was consistently correct. Any ideas besides creating a VFP COM object? Or should I accept Fox 2.x ODBC reliability over performance--dumb question?
>>>
>>>Thanks in advance...
>>>
>>>Regards,
>>>
>>>Jack Mendenhall
>>>RMI