David,

There is one good reason... Some calls to CREATEOBJECT include the class library because there are classes with the same name in different libraries, so a search through all loaded libraries for a specific class name wouldn't necesarily return the correct class.

If I'd known before hand this kind of issue existed, I would have taken steps to ensure all class names were unique, however thats not the case and hind-sight's 20/20, meanwhile, I have a huge application with a serious problem.

Thanks,

- Aaron.

>Aaron,
>
>For what you are doing there really is no good reason to specify an alias in the SET CLASSLIB.
>
>>However, what I've stated is that I "am" supplying unique ALIAS's for the Classlib's I'm loading,
>>But, those are being "changed" by something not under my control, which I would typically label a BUG.