>>>>I have a process that joins two tables wihtin a SQL Server
>>>>stored procedure and the result set is pulled down to a
>>>>VFP 5.0a cursor. The size of the result set is 200 records.
>>>>
>>>>We noticed that the VFP cursor is irratically being
>>>>corrupted after being queried via joins. The cursor has read/write
>>>>capabilities, but is never written to (no edits or adds).
>>>>Two index tags are added to the cursor.
>>>>
>>>>The time this was investigated, about 60 of the 200 records
>>>>were corrupted as follows: All numeric type fields went to
>>>>0 and all character are CHR(0).
>>>>
>>>>Anyone else experienced this or have a solution?
>>>>
>>>>
>>>>Tom Bellmer
>>>
>>>
>>>I ran into a similar sort of problem about a year ago. I think some of the fields had garbage characters or CHR(0) but when I ran the same query through Isql/w it retrieved the data correctly. I believe the problem was with the ODBC driver and I updated it. I think the driver is SQLSVR32.DLL The one I have is version 2.65.0240.
>>
>>I will look into the ODBC issue. However, it seems as though
>>the data is good when initially pulled down and only after some
>>querying does it get corrupted. Did this happen to you or was it
>>bad from the get go?
>
>I don't very often query the result sets, if that is what you are doing. Are the joins against all local tables or are they also using remote views?

We are not using remote views. We are using calls to stored
procedures to extract data from reference tables and using these
fox cursors to validate data. After the SQL SP calls we do not
use SQL Server or remote views - all data from then on is Fox tables
or cursors from SQL Server.