>>Keeping it as UDF saves me the overhead of CreateObject()ing a DateBox, just to call its methods as UDFs.
>
>"Premature optimization is the root of all evil." :) And I wasn't suggesting a (visual) DateBox class, but a nonvisual Date class.

Mmmmmmm... not a bad idea at all. The DateBox should need to have one of these as a member... why not. Fits... and results in an avalanche of similar groupings of functions. I guess there will be only a dozen left as UDFs.

Though, it raises another issue: knowing which class has them :)