>There are about 2000 records in the table. Also, when I say I "run" it.... I'm talking about executing the exe and the initial page displays and then exiting the program without doing anything (no adding of records, etc).
>
>I notice that the size of the CDX goes up by exactly 25,600 bytes when I run and exit like that.

A CDX file size of 1.2GB on a table with only 2000 rows is much too large. Probably there is some sort of corruption in the CDX file which is giving VFP fits. I agree with Chris, the first step is to rebuild the CDX as he outlines.

There are no user data stored in CDX files so it's safe to delete all tags, then rebuild them to re-create the CDX. One minor exception would be if the table is in a VFP DBC "database" and table relations/referential integrity is in place, where deleting tags could break that, but presumably you're not doing that.

... or are you? Might you be using DBCs and triggers etc. in some way?

If you're using some sort of exotic antivirus or other file system utility you might want to test by excluding the folder that contains the CDX from any real-time scanning or backup.

Another thing I've seen on a few occasions cause problems with index files is the presence of unexpected characters (especially CHR( 0 )) in the DBF data table. Usually this can be seen as a vertical black bar in a character or memo field. You can use interactive VFP commands to search for these e.g.

USE MyTable
LOCATE FOR CHR( 0 ) $ MyCharacterField
LOCATE FOR CHR( 0 ) $ MyMemoField
* etc.