>>You may have a SET CLASSLIB to the questionable class somewhere. I usually SET CLASSLIBs when I startup VFP. Issuing a RELEASE ALL or CLEAR ALL; I do both will solve this.
>
>I often experience this problem after I've run a form which uses the class. My guess is that VFP isn't releasing a reference to the class. I have a macro set up to rerun my startup program which sets global variables, issues SET CLASSLIBs, and, as Ramil suggests, issues RELEASE ALL or CLEAR ALL commands. I can then check out the class with no problem.

Might need a cancel all, too.