>Hi Tom,
>
>I had not heard about this problem earlier. Can you post the SQL here? Maybe its coming from there....
>
>>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

Well it looks as if this is a known problem with VFP 5.0
and SQL Server 6.5. The solution according to knowledge
base article Q164385 is to maximize the buffer size by
setting both SYS(305,1) and SYS(3050,2) to the value of
SYS(1001). This solution seems to work in the limited
number of test that have been performed.