Isn't OOP great. Solve once use everywhere.

>Good points. I just subclass a txtBox for each type and use that. (Evan turned me onto that a couple months ago.)
>
>>Technically, I agree. Practically, I disagree. In most cases, I will store tel, zip fields with formatting because then I can just drop the field on a report, or drag it onto a form and it will display correctly. Otherwise every end use of this field requires formatting. eeuw.
>>
>>>I gotta agree with most of the other posts. Your data should be like pudding and take on the shape of whatever the UI dictates.
>>>
>>>
>>>>Hi Folks.
>>>>
>>>>The "R" Format property. You know, the thing that applies a format mask to data as specified in the InputMask property. The Builders love it. I don't. Phone numbers, for example. If the data is stored as (999) 999-9999 and you use (999) 999-9999 as your InputMask and have R in the Format, you end up with a display that looks like "((99) 9) 99", or something to that effect.
>>>>
>>>>Frankly, I like to store data as formatted so that I don't have to worry about formatting it from whatever front-end I get it from. So the "R" is worse than useless for me.
>>>>
>>>>What do y'all think?