>The most obvious reason would be that the SET CLASSLIB statement is missing.

It's the same code, thus same EXE. It works at one place and reports that message in another place.

>It would also happen if one of the parent classes is not included into the EXE. It might work on the other machines, since VFP tries to locate the external the VCX file in this case. A common scenario is if an application is split across multiple EXE to make distribution easier. This doesn't work very well with VCX classes.

On the production machine, there is no sources. It works. This is the same as in the new server. Yes, it's coming from a sub EXE. So, that means there is a non accessible item from that level. However, it is quite strange that it works in one place and not in the other.

>It could also be that the CREATEOBJECT() line is executed from an external file that is not included into the app. In this case, VFP might have switched to a different application session and doesn't find file included into the original EXE. A sample is if an external SCX is called from an EXE and that SCX calls another external SCX. In this case, the second SCX might not have access to any file built into the EXE.

I will do more research and will tell me once I find it.