Hi John

If you are using a visual class then yes you need to specify the module also

NEWOBJECT(cClassName [, cModule [, cInApplication [, eParameter1, eParameter2, ...]]])

But in a non visual class there is no module and for reasons I don't quite understand the application name moves up one parameter.

I have managed to find a partial solution. It involves using SET PROCEDURE TO and then having a loader function that uses SET CLASSLIB TO for the base classes (could also use SET PROCEDURE TO but in this case I have a number of visual objects which are better maintained in a visual way). The function also creates and returns a pointer to the derived object.

This actually gets me around another issue. That of being able to store my functions in a DLL. I am somewhat wary as in the grande scheme of things there is the potential for duplicate base class names to arise.


Regards
Geoff

>Geoff
>
>Don't you need to pass the vcx as a parameter before the exe?
>
>Regards
>
>j.R