Hi Shih!
Probably it would be better to instantiate this class via createobject()
once at start of application. By this way, it will be not necessary to drop
the custom class to the form. BTW, I use this method for my Utilities and
Sysinfo class (works just fine)
>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.
* Human is a question asked by birth and answered by death. Machine is another kind of question with another kind of answer
