Justin,

We are having exactly the same problem. We're running VFP 6, SP5, SQL 2K SP3, Win2K SP3.

We're creating the 'schools' cursor using SQLEXEC, and then creating an index on the cursor like this:

* force all records down
SELECT schools
GO BOTTOM
* create index on schools by code for later processing
INDEX ON schoolnum TAG schoolnum

Everything seems to be fine until we have done a bunch of processing on other files. Then suddenly we start to see CHR(0) in some of the fields.

My current theory is that creating a CDX on the cursor is somehow 'hosing' it, but it's difficult to test because it is intermittent, as you know.

We have tried doing subsequent selects on the cursor to eliminate the need for the CDX, and that seems to make the problem disappear, but again, it's hard to know for sure since it's hard to duplicate the problem.

How are you creating the indexes? Are they CDXs or IDXs? Have you tried doing the 'USE DBF('cursorname') AGAIN ALIAS newcursor' thing and indexing on that cursor instead? (If you have no clue what I'm talking about, let me know and I'll 'splain.)

>I am having a intermittent problem where the data of some records in a cursor are being replaced with chr(0).
>
>I have an application that creates and indexes some small Visual Foxpro cursors from SQL (using SQL EXEC) and after some intensive Foxpro processing some of the records have chr(0) in all their fields instead of data. The weird bit is that underscores are not replaced with chr(0).
>
>I've seen this type of thing before in data when the table or cursor has a corrupt index. I don't think this is the case this time, but could this be due to memory problems?
>
>The setup I am using is VFP6 SP5 / SQL 2K SP2 running on W2K server SP2.
>