Good morning Cathi,

I do some try and error. It is simple. I put the vcx's needeed in a new project, compile (as you mentioned it links all related stuff) Set all I didn't want to "Exclude".
Then I compile again to an app.
If I do loExtern = NEWOBJECT('My_Class','My_VCX','Extern_App.app') the object is instantiated. It simply picks up the vcx's in my main EXE.

I have not checked pictures since they come from my base classes.
Now I start with frx ::)

Agnes

>>Hi Cathi,
>>I see the point.
>>My sources are all vcx, frx, mnx. I've cleared all scx and most prg's out of my projects. Some bitmaps and icons are needed.
>>I don't like to scatter this on customers pc.
>>The question is: Do I need to include the parent classes in an dll? Or can I refer to that included in my main exe?. It never needs to run for itself. It must be just a wrapper I can access from my main exe. I would like to create objects out of this wrapper with [.]NEWOBJECT() .
>>
>>Agnes
>>
>>>You have several options here. You can mark the source files (prg,scx,etc.) as "Excluded" in the project and just place them in the directory that contains the EXE. Then you can use the DO command and reference the locate and name of the source file. For example:
>>>
>>>DO mymethod IN myfile.prg
>>>
>>>Another approach is to create a separate project and build an APP, EXE, or DLL. When the project is built, it will try to include any references to external libraries used. This approach is typically used it these external files could be used without the main EXE. Your external application will be larger in size then just using the source code. The one disadvantage with just including the source code is you are exposing that portion of you application to have other developers modify it.
>
>
>When the project is built to create the DLL, the parent classes will automatically be included. It needs to resolve all the dependencies. The DLL is built to run external to the main EXE.