Aaron,
I think you need to add some debug code to test the current classname right before the createobject call. I'm betting that the name is either invalid or your classlib path no longer contains the correct classlibs.
>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.)
