>>I agree with Tamar, and for this type of app I'd normalize phone numbers.
>>
>>I went through this for an app for a veterinary hospital. People were always coming in saying "oh, please call my husband's office when Fluffy is ready to pick up".
>>
>>Since Husband may actually exist on the database, but with a different last name, it could be difficult to locate the number. (Likewise, they'd occasionally have a phone number and ask "who all is at this number?")
>>
>
>I can't think of much of any application today where I'd do phones with a fixed number of fields instead of a separate table.
>
>Tamar

Yep. Anything less invariably ends up being more work than necessary.