>> Hector's idea is somehow easier to implement
>> (I just have to convert form into custom (or
>> line) class).
>You wouldn't need to convert the form to a class. You could just move the methods that do the standarization process to a class. That way, you just would need to modify the UI to call methods from the class rather than code inside the form. Still, your form would still be a regular form.
>
>If your new "standarizator" class is a VCX, then you would instanciate it either by dropping the custom class inside the form (at design time) or by issuing (at runtime) a call to CreateObject in one of your methods.
>
>I agree with you about performance. I don't think that using a class will impacte performance whole lot since, once the class has been instanciated, using it will be just a matter of calling its methods.
>
>Still, whether you should use UDFs or a class is a decision that you should make. Either way will work, it is just a matter preference with pros and cons on each side.

I like this idea and will proceed with it.