We also use one custom class to hold common routines. To minimize overhead we instanciate it in the startup of the application object and use a property of the app to hold the reference to the common class object. For example. in the application startup:
goApp.oCommonCode=createclass('commonobject')

and in the other parts of the app refer to the functionality as

loParms=createobject('parameterObject')
loParms.somevalue=whatever
loParms.othervalue=everwhat
etc for any other parameters

goApp.oCommonCode.method(loParms). We also use a custom class parameter object for most calls and return values using it's properties.

lcValue=loParms.returnvalue.
...

HTH


>I have some functions that are shared among a few forms. Currently, I am using a 'Custom' class to store all the functions and this class is dropped into the form that needs any function. I am wondering if this is a bad way as compared to SET PROCEDURE TO. I like the visual aspect of Custom class. That's why I do it this way.
>
>Any advice?