Are you using grids? That object seems to be so complicated, Fox6.0 debugger doesn't handle all the situations. I've run into times where I had something coded wrong, and the error wouldn't show up until I got the C05 at runtime. Of course, there's no clue to tell you what's wrong, but once the bug is fixed, the problem goes away.

I have one project that uses no objects, just straight code with lots of function and program calls containing SQL SELECT statements and SCAN/ENDSCAN. Running in FoxPro, the program never returns an error. In runtime, it always does. I found a work-around by taking the erroring program call to the earliest position possible in my list of calls, and putting a CLEAR ALL at the beginning of the program. For some reason, CLEAR ALL behaves differently at runtime, and cleaned up whatever is left in memory that was crashing my program.

Sorry I couldn't be more help.

Yes, I am running SP5.