>Here I go again against the grain... I think it is a mistake to use "set classlib"; and the whole purpose of newobject vs createobject is to handle this, in my opinion.
>So, you either use newobject (method or function) without "set classlib" (my preferred way, in fact the only way I use it) or you use createobject (function) with "set classlib" (I only use createobject for activex, even when I know I could use newobject for it too), but there is no point in using newobject with "set classlib". I know from past discussions that there is some consensus here that I am wrong and "set classlib" is useful, but I am also stubborn :)

I'm decidedly on both sides of this :) (i.e. I'm a stereo type, working on both channels as usual). The framework classes get loaded in a series of set classlib and set procedure statements at some point in startme.prg; those get createobject()ed frequently and in many places. The local classslibs, i.e. those which contain a few related forms and any related objects, are newobject()ed, with class name and library stored in metadata. That way the set("classlib") and set("procedure") lists don't get too long. Which may be a ridiculously minuscule speedup with today's machines, but as they say, habit is a trouble, unhabit is two.