Hi Jon

Yes, that works also but the when using NEWOBJECT to create a class derived from another VCX requires the definition of that class to be present. For some reason, even though the base class VCX is included in the project NEWOBJECT cannot find it unless it has been specifically loaded via a SET CLASSLIB TO.

This seems to me to be wrong and runs the potential for the wrong base class to be used when creating the derived class. It shouldn't happen, I agree, but it could.

If the build process is smart enough to add the VCX when it builds the exe, you would think it would be smart enough to know where the definition is.

I have tried using the OF clause in the class definition but this bombs out because this class library contains a number of definitions from which objects are derived for the TestInterface project. Even if I make all the derived class definitions no visual I still get duplicate name problems. It may be that I need to split all of the base definintions out into seperate class libraries. This seems self defeating.

Regards
Geoff Scott

>Geoff,
>
>If the class is stored within a PRG in the TestInterface project, then I think that the module parameter in NEWOBJECT() would correspond to the name of the PRG and the application parameter would then be TestInterface.exe.
>
>Laterness,
>Jon