Hi Fred,
Unfortunately this is the way it works. Steve Black wrote a utility which goes up to Class Heirarchy and puts everything into one VCX. I think it should be there on his web site at www.stevenblack.com

>Would you consider this to be correct behavior or a bug?
>
>If you have a class lib contained in an .APP/.EXE (included) and another class lib that that is excluded from the .APP/.EXE that subclasses things from the first class lib, where would you expect the excluded class lib to look for its parent class? I would have expected it to look in the included class lib, but it appears to actually look at the separate class lib .VCX on the disk.
>
>IE:
>You have an included classlib MYBASE.VCX and an excluded classlib MYSUB.VCX in MYAPP.APP. And you distribute MYAPP.APP and MYSUB.VCX, you get errors instantiating classes from MYSUB.VCX, even if you specify SET CLASSLIB TO MYBASE IN MYAPP.APP. If you actually provide class lib MYBASE.VCX is seems to work, but that's not what I expected to happen. If MYSUB.VCX is included, too, then the only thing you need is MYAPP.APP and everthing picks up the included VCX's, as expected.
>
>Does this seem right to you?
>
>TIA