>>I've tried an example similar to yours with both a SET PROCEDURE TO and SET CLASSLIB TO and it finds everything just fine. I even made sure I moved the .PRG with the classes (and any .FXP that may have been laying around) and the .VCX/.VCT with the other classes to a different folder. As long as my two .EXEs were together, or I specified the path to them in the SET PROCEDURE/SETCLASSLIB commands, everything was found at runtime just fine.
>
>I'm using VFP 7.0
>
>OK just to make sure I understand everything you have:
>
>myMain project has :
>all the classlibs in it, but they are excluded.
>myMain.prg contains "set procedure to myProcedures"
>myMain.prg contains "set classlib to myClasses in myClassLibs.exe"
>myProcedures.prg
>There are no prg classes.
>
>myMain.exe has :
>no classlibs in it.
>It has myProcedures.fxp in it.
>It has "set procedure to myProcedures"
>It has "set classlibs to myClasses in myClassLibs.exe"
>
>
>myClassLibs project has :
>all the classlibs in it
>A Main Program with nothing in it except a comment.
>myProcedures.prg, but it's excluded.
>Nothing else
>
>myClassLibs.exe has :
>all the classlibs in it.
>No "set classlib" or "set procedure"

OK, I know I've done exactly what you have here in the past (using VFP6). My sample that I was testing with had my procedures (with DEFINE CLASSes in it in the MYCLASSLIB.EXE, along with the MYCLASSES.VCX. I am using VFP8, not VFP7, so there may be a difference there. I don't have access to VFP7 where I'm at to test what you've got.