In regards to the long distance number and needing to list them with a 1 in front, is there a way to make the verification programming allow the "1" in front? If a number does not conform to either of the two formats, i.e.:
On the phone numbers - one thing you might have to consider is the long distance issue that Jim mentioned. That's one that plagues us as well when tracking phone numbers.
We have some people within our area code that are long distance. It doesn't matter on a cell phone, but if I'm calling from a land line, I need to know to dial 1 first. Otherwise, you get a wrong number or bad number. That's hard to indicate in restricted format fields.
As far as the email field, I like format verification on web input forms, but not in my databases. If the data is bad (and some emails always are in any given list), I'll know when I send a bulk message and take appropriate measures.
Then again, if restricting the fields satisfies the majority of users, that's what you need to do. There's no way to make it perfect for everyone.
JHB is right about emails. The only downside about relaxing the email verification standards is that certain bad emails in the system can cause very bad things...so we tend to err on being more restrictive. We will look into this however as we review potential enhancements.
As for phone verification - that is not something we have heard before. I do think there are benefits for the verification as it prevents lots of typos. My gut is this one is less likely to be done.
PresidentJim - changing software is a house of cards. Sometimes what seems like a simple change has much wider implications, especially when it comes to adding or removing fields. But changing field validations usually isn't too hard - maybe they'll be able to go that route for both of these issues, at least as short term solution.
I'm not crazy about telephone field validations. It's rare I'd be transfering data to a device that allows for auto-dialing, so I'd rather have the freedom to have a 1 in a field to remind me it's required, or add an extension number.
Sure, I understand how the same person could be e-mailed twice when that wasn't what the person sending the e-mail wanted, but at the same time couldn't an if/then/else be written in with a check box toggle control? Check which e-mail(s) you want to have as the default.
Another minimal thing that I found is that the phone number verifification would not allow me to put a 1 in front of the number. I have some members who have a work phone or a cell phone that is out of area. If I dial the number without putting the one in front I get the "you must dial a 1 before the number" message, so I like to list these numbers with the 1 in front. I wasn't able to do that.
Is there someway that that could be allowed?
Thanks and I am starting to fall in love with this program.
PresidentJim
That is a great suggestion but unfortunately we do have email validation in those fields. Allowing your suggestion is probably much more feasible than adding a second email address field which will impact the program is several other ways. For example - if we do have a place for 2 emails then many users will complain when get the same message twice and that will force the school admin to go in and remove one of the emails....
