>>>>That was more of a reference to the FFC class libs, not yours. I had to do nothing special for the two .EXE's to work together, just make sure that the MYCLASSLIB.VCX was excluded from the MYPROG.EXE. I even renamed the MYCLASSES.VCX/.VCT files after I built the MYCLASSLIB.EXE to make sure it wasn't using the .VCX directly when I ran the MYPROG.EXE.
>>>
>>>Just out of curiousity:
>>>Did you create myClassLib.exe with ONLY the vcx files in it? If so, what did you use as the Main program in order to allow the Build?
>>
>>All I had was myclasslib.prg with a comment in it.
>>
>>

>>* MYCLASSLIB.PRG
>>* stub to allow building an .EXE for MYCLASSES.VCX
>>

>
>OK, that's what I've done.
>My classes reference prgs that I have in a Procedure file. I had to put the procedure file into the project in order to get rid of errors, but I excluded it from the build.
>Did you do anything like that?

If you've got a proc file with DEFINE CLASSES in it, you'll need to have a SET PROCEDURE TO yourprocfile IN myclasslib.exe where ever you've got your SET CLASSLIB statement. You'll need both in order to find both procedure base classes and visual classes.