>Thanks a lot, Hector. I was starting to write a private e-mail to one of the members to ask him to check this thread at this same moment:) I think, it's a good idea and so I'm going to create a visual class. I may even try to convert my form into custom class (will experiment) and will eliminate all unrelevant code...
>
>Thanks for confirming my thoughts about it...
I don't know that making the form a class is better. Why dump a UI in a class that won't always need it? I would think about making the "Address Standardization Portion" a class by itself. Maybe even make it a .DLL.
Now the Form can use that class, and/or any other parts of the that or another app can use just the class/DLL.
Roi
'MCP' Visual FoxPro
In Rome, there was a poem.
About a dog, who found two bone.
He lick the one, he lick the other.
He went pyscho, he drop dead!