Aaron.
We had something similar, where I could not explain why the Classlib seemed to be dropping things. After moving to the NewObject() function instead of the CreateObject() the problem no longer exixts. NewObject(), is much better in that you don't give a hoot about the classlib, which could become long and unwieldly.

Regards,

- Glen -

>I have a routine which instanciates an object using the CREATEOBJECT() function.
>
>My problem is, when this routine is called a number of times in succession, eventually it will generate the error "Class Definition is not found."
>
>This doesn't happen ALL the time, but clearly it's not just a case of "well you have typo in the class name", or "you haven't used SET CLASSLIB", because it works "for a while".
>
>It's as though VFP is dropping the class from memory (wild guess.)
>
>Any ideas or solutions?
>
>Thanks,
>
>- Aaron.

- Glen -

The impossible we do immediately.
The miraculous will take a little longer.