>Possibly a pathing problem? Does the routine causing problems change path at any point?
>
>>I have several applications that use the same approach to error handling. In the startup routine, I have the command ON ERROR DO EHANDLE. EHANDLE is a short program that sets up some parameters and then calls a form called EHANDLE that resides in one of my class libraries. The code looks like this:
>>
>>frmError = CREATEOBJECT('Ehandle', "suggest")
>>
>>Most of the time, the error handling system works just fine, but in one of my applications (and only that application) the application will occasionally encounter an error, call the ehandle program, and then give the user "CLASS DEFINITION EHANDLE NOT FOUND" after that, the user usually ignores the problem at which point VFP returns the error frmError not found and then crashes out to the operating system. The appropriate SET CLASSLIB commands are issued at the begining of the program, and (as I have already said) most of the time the system works. What would cause VFP to be unable to find a class definition that is compiled into the project and available to the program most of the time?
>>
>>Thanks in advance..
>>
>>jd
Barbara and Jim:

Thanks for your interest. I found the problem. After getting my user to walk me through the problem step by step, I found a SET CLASSLIB TO command left over from the design aspect of that particular form. It was killing all the CLASS LIBRARIES. Once again, thanks for responding...

jd