Heya Peter -
first - a clarification -
I meant to type 'filetostr' and not 'strtofile'

IN MEMORY ?
you can create an object on the fly and add in methods at run time to the object, with the methods being IN the contents of a memo field, and
then you can reference the methods from an object call.
OR
you can do a strtofile() and then eval the contents to an object
OR
you can do a strtofile() and then run the execscript beastie against it .


>What do you mean with IN MEMORY?
>
>Peter
>
>
>>Heya Chris -
>>after reading all of the thread replies to your posting -
>>I would suggest that its time you move on from multiple class libraries
>>
>>and make either:
>>1. a prg file that contains all that you want. Compile it encrypted [cause you want to resell it ] into an app. and then reference the app earlier on in your program calling hierarchy.
>>2. a complete raw dump of the '2 levels of instantiation that you need' into a memo field - then eval/exec the contents of that memo field
>>either via strtofile() or IN MEMORY
>>and have your class libraries reside only in memory during program execution.
>>It's a tad bit convouluted - but at the same time ?
>>once you got it IN memory -
>>you don't have to worry about 'which' baseclass you are subclassing from.
>>
>>HTH - mondo regards [Bill]
>>ps -
>>classlibs are really tables - so study them a bit with scan..endscan constructs, and see how you can sling code into memory with a scan..endscan loop.