>>
>>This function saves a lot of code when creating objects. You don't need to open all classlibs in the startup program yet you can create objects from those libraries by using the NewObject function.
>
>But aren't there some serious performance hits for this? I seem to remember something in FP Advisor to that effect.

Theoretically, the difference is just like between having a Set Procedure issued in advance, or saying "do this_proc in that.prg". The "That.prg" should be included into the search list; will it be included sooner or later doesn't matter much. I believe the other approach may be a bit quicker, because it's explicit, i.e. the search goes directly there. Therefore, NewObject() will look directly into the .vcx you name, instead of searching all the "Set classlib" libs in the list. Though, there'll be some delay while it opens, but the other way 'round you'd have the same delay while setting the classlib to it. No wonder difference isn't worth noting.