phone number input mask with an optional extension

[Guest]

How would I use an input mask in an Access form to allow for an optional
extension?
w/o extension: (999) 000-0000
w extension: (999) 000-0000 x 0000
I would like for the " x " (that's an "x" with a space before and after) to
become part of the data IF there is an extension, without having to type it.

 

[(PeteCresswell)]

Per JamesInTX:

How would I use an input mask in an Access form to allow for an optional
extension?
w/o extension: (999) 000-0000
w extension: (999) 000-0000 x 0000
I would like for the " x " (that's an "x" with a space before and after) to
become part of the data IF there is an extension, without having to type it.

This has called out to me in the past, but every time I got into it turned out
to be a can of worms.

Right now, my philosophy on this is that phone numbers are raw text fields:
anything goes.

There are just too many combinations and permutations to deal with - overseas
dialing sequences/formats, for starters. Variable extension formats for
another.

 

[Guest]

Thanks Pete,
I can't say I will never have overseas numbers/formats to deal with but
haven't in the past 15 years or so. I'm using this for personal use as well
as for a local group. I'll deal with overseas numbers and variable formats
when the issue arrises...LOL

 

[(PeteCresswell)]

Per JamesInTX:

I'll deal with overseas numbers and variable formats
when the issue arrises...LOL

Then how about four separate fields:

Area
Exchange
Number
Extension

Then you could deal with extension separately when time comes to format a phone
number. Obvious downside is inconvenience in data entry...