>>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?
>
>It seems to me that using a Custom Class is the best way to approach this issue since it is often beneficial to be able to address things generically... as in... THISFORM... THIS.PARENT. and so forth. You lose that in external procedures.
>
> Tom


Get Drew Speedie's MaxFrame. In it he talks about procedures
that are better to place in a SET PROCEDURE file and those
that that work better in a class.

Dan