Hi Christoff,
Can you elaborate on 'an application is split across multiple EXE... doesn't work very well with VCX classes.'?

Our MIS application consists of an EXE root that calls the most recent compiled EXE main (mainly an applications menu) and then each application is another EXE (that may, in turn call general utilities type EXEs)
We include all our class lib in all our projects.
We always use NEWOBJECT which lets you specify the class library (so we don't need SET CLASSLIB required for CREATEOBJECT)
Now, from time to time, but always after going from one application (i.e. one EXE) to another, we get the error saying that the class definition cannot be found... on a line with NEWOBJECT() statement.
Thanks.


>Hi Michel,
>
>>But, as soon as come time to createobject('something'), it says that class definition not found for the something.vcx file. Anyone has any idea what could cause this?
>
>The most obvious reason would be that the SET CLASSLIB statement is missing.
>
>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.
>
>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.
>
>--
>Christof