>Hi Fabio
>
>Bit late on this thread but I got a very similar error when VFP couldn't find a class library. The library existed and it was in the path but for some strange reason Fox could not find it. I can't remember exactly what it said but it presented an informational type dialog. As far as I was concerned it was an error because everything was where it should be. I wrapped the offending code in a TRY/CATCH block but no joy ... the dialog kept coming back telling me that it couldn't find the library. Not great when displayed to the user.
>
>Bye
>
Angie,

The problem may be caused by referring to the class library with the fully qualified path. In a rather short answer, "Don't". Keep the class librarys on the Fox path, and only refer to them by name. For example, SET CLASSLIB TO MyLibrary. At run-time, since the library is built into the executable, there won't be any problem.