I would say that a class (either in a VCX or in a PRG) would be better.

"Complicated UDF" can be replaced with simpler methods inside the class to do specific things. Properties in the class can help you reduce the number of parameters in methods (if the class is state-full.) In general the code will be better encapsulated with a class.

Just my $0.02


>Hi everybody,
>
>I have an application called Address Standardization. This application has user for with grids, command buttons, lots of custom methods and properties, etc.
>
>Recently I was assigned to write a program to perform automatic standardization without user interaction (to correct obvious and easy problems in our whole database). Of course, I'd like to re-use the code, I already developed.
>
>So, the question is: how to make most advantage of the developed code and how to organize it? Should it be a complicated UDF with subfunctions (as my manager thinks for this task)? Or should it be a custom object?
>
>What would be your suggestions?
>
>Thanks in advance.