>>>When you run a program that will use these classes, SET PROCEDURE to each of them.
>>>As long as it's in memory, it will find it.
>>>Be careful not to have identically named classes in each prg, otherwise it will just use the first one if finds.
>>
>>So the answer is a third .PRG? I'll give that a try, thanks.
>
>Well, that's not the answer really. The answer is the SET PROCEDURE TO to bring these prg's into memory, just like you would to be able to access a function within a prg.
>
>You would most likely SET PROCEDURE to the subclass's prg file, so just set to both while you're at it.
>
>You could also include both definitions in the same prg - no harm in that.

My problem is that is seems reasonable to keep your base class in a seperate .PRG, yet there is no way to do a SET PROCEDURE in the child that will allow this. I tried using a third program with a SET PROCEDURE before creating the child class, but it only set the procedure in the third program, the child class didn't find it.

I would think someone would have run across this before.