>>>I don't see why class is better or worse in this case. The only difference would be that in class you can use properties or pass parameters and in UDF you can use parameters only. I'm not sure if class wouldn't introduce some overhead that could be important if you process a lot of records.
>>
>>Ok, now what? :) I now have two valuable opinions (as allways about theoretical questions :)). Hector's idea is somehow easier to implement (I just have to convert form into custom (or line) class).
>>
>>UDF is not that easy to maintain. I'm not sure about overhead, I don't think it would be much...
>>
>>I'm going to process lots of records, but this would be a method inside class, e.g. it would be a DoProcess() method, which would scan the file...
>
>I guess I misuunderstood you. I thought you were going to separate Address Standardization "engine" and use it in the form and automatic processing.

No, the Address Standardization application is completed and has a user form. This new class I'm going to create would be based on the form (I need to convert the form). It would be a completely separate thing..., though it may become a part of Address Standardization application. E.g., if I would call it with Auto mode, it would use the class instead of the form - hey, I just inveneted this idea in this message. Looks like a plan.