>I'm wondering if the many C5 errors that I experience during normal edit, build, run cycles are related to the fact that I am using VFP 5.0 and Windows 2000 Professional?
>
>Does anyone else use this environment?
>
>At this point my experience is that Windows 2000 is much less reliable than Windows 95 when working with VFP 5.0. Alas...
>
>Peter Robinson

IIRC you're a Visual FoxExpress 5 user; is the problem you're seeing actually persistent C5s while doing VFE builds? If so, you know that NT4 has a lot of problems with that, and for maximum stability W9x is actually the preferred platform. Mike & Toni never determined what the problem was, speculation was some sort of bug or memory leak in the ActiveX control(s) used in the VFE UI.

The very general impression I got with this problem is that personally (running on NT 3.51) I got them more often when there was less memory for VFP (i.e. multitasking other things at the same time). If you're under 256MB on W2K it might be worth adding some, just to see.

Actually, something else is ringing a faint bell... I seem to recall one fairly hard-core user going through the entire framework and re-coding all sections that use more than one PEMSTATUS() in a single IF construct. He posted a fairly extensive message to that effect on the F1 Forum; again, IIRC that cleared up a lot of C5 errors for him. Sorry, I can't recall the exact message or who it was, but you can probably find it using Search.