>I am getting tired of adding phone # fields to various tables as users come up with new requirements. I am thinking of creating a phone # class for the whole application. The functionality would be like the phone # fields in Outlook Contacts. I would have one table for all phone #'s. There would be a phone type table that described the type of # (home, work, fax, etc.), the parent table for the type, and sort order for displaying the types. The phone # table would contain the #, the PK of the type record and the PK of the record in the parent table. The class would consist of a textbox for the # & a dropdown list for the type. It could be dropped on a form as many times as needed.
>
>If a user wanted a new phone # type, I could just add a record to the type table and it would be instantly available.
>
>Has anyone done anything like this? Is this overkill? Am I crazy?
>
>John

You might want to take a look at FullContact from F1 Tech: http://www.f1tech.com

It does this plus a lot more. We just had Dave Tansey and Mike Feltman up to our recent user group meeting demoing this. It's pretty cool.