Hi Garrett

Index corruption is not likely since the indexes are rebuilt every night from scratch (ie I delete all the tags and rebuild them). I am using free tables so there is no RI.

If index corruption does turn out to be the cause despite the rebuilding every night what would be the cause of this corruption. The application ran fine for years without index corruption. The change occurred after moving to VFP 7.0.

Simon

>>I changed the line to :
>

>> Scan For PID=ARTrn.ID.And.!EoF() NoOptimize
>>   Delete Next 1
>> EndScan

>>
>>(I realize that I do not need the !Eof() clause it is a habit from the pre-scan days of FoxPro.)
>>
>>Since I have made that change to turn off the optimization I
>>have not received a C5 error in 17days and counting. Previously
>>I would see some every week.
>
>Hmmm. You could have some minor index corruption. Have you tried deleting all your indexes and recreating them from scratch? If you have RI set up, this will cancel it, so you might want to look into using Stonefield Database Toolkit.