Pete Dashwood wrote:
>>
>
> Jeff, here's a thought: Why validate phone numbers at all?
>
> They are NOT valid unless you actually dial them and get a pick up.
>
> Phone numbers can contain all kinds of characters: +64 7 1234567,
> 1-800-CALLME, ... not just dashes. It is a pointless validation.
>
> The primary use of this information is so a Human can use it to make
> a call. Humans can see immediately whether what is recorded is a
> phone number or not.
>
> I get really annoyed with Web pages (for instance) that try to
> validate a phone number and DON'T recognise + (the symbol for your
> international access code) or ALPHANUMERIC phone strings. in fat, as
> a user it is so frustrating to have a page constrain you to what some
> programmer considers to be the "right" way to enter a phone number,
> that I have simply gone and shopped elsewhere. I figure if their data
> forms are not friendly, there is no reason to expect their company
> will be friendly if I need service or sup****t.
> In my systems I don't validate phone numbers and no one has ever
> complained.
> I completely agree with HeyBub that only numbers you intend to do
> arithmetic on should be stored as NUMERIC types.
>
> That rules out phone numbers.
>
Your community is evidently not plagued with robo-calling machines.
In the U.S., these machines call the number and when you pick up, the call
is routed to the next available agent. If you don't pick up, the machine
goes to the next number.
There is sometimes a significant delay between when you pick up and when a
human gets on the line. Often, when you answer, you'll get the message "We
have an im****tant call for you. Please hold the line."
After a wait, a voice comes on: "Hello, may I speak to Mr. X, please." To
which I respond: "I'm sorry, he's no longer with us. You've reached the
Suicide Prevention Hot Line. Can someone else help?"
|
