It will take more time to newobject() because memory has to be allocated. However, as fast as computers are today, I don't think you'll notice the difference.

You could also go a hybrid route and use a class factory. The class factory would load the classlib or procedure as needed, then just keep a reference to it. That way, things are only loaded if needed, but kept after that.

>Thanks for the feedback.
>
>I've used newobject() in other projects but this particular one is inherited code that, as I've mentioned before, uses set classlib.
>
>The thing that I'm still unsure of is, does using newobject() reduce system resources (or offer other advantages other than not having to set classlib) when compared to set classlib? If it does, then I'd attempt to switch over to using newobject() instead. If not, then I wouldn't bother.
>
>Mike