Peter,

FWIW, I still use maybe 20 UDFs in my development. I don't think making them a method of some object makes them any more accessible, in fact it tends to hinder their use because you have to instantiate the ProcedureObject. I also don't use a monolithic procedure library. Each udf lives in it's own file, the filename matches the UDF name so you never have to SET PROC anywhere, you can just use them like builtin VFP functions.

>Now, I would like to have this function handy to use. Should I create
>some kind of date class to contain this and other methods or just
>put in a procedure library? My inclination is to do the latter.
>
>Or looking at it from a different point of view: VFP has gazillions of functions. Is this a problem that they are not methods?