ChronoForms validate-alpha rejects hyphenated last names in an inputbox.
I find no other validation which will accept a text & hyphen in the content of the inputbox. I suspect the hyphen is validated as a mathematical operator & the input is rejected with an error message.
I need ability to process people in my database who do have hyphenated last names via a ChronoForms.
Is there another validation which allows such or do I need to construct one? Where are the validation routines stored?
I find no other validation which will accept a text & hyphen in the content of the inputbox. I suspect the hyphen is validated as a mathematical operator & the input is rejected with an error message.
I need ability to process people in my database who do have hyphenated last names via a ChronoForms.
Is there another validation which allows such or do I need to construct one? Where are the validation routines stored?
Hi Rlaurel,
The alpha validation does exactly what it says on the box and not a penny more :-( It is not suitable for most name fields where you may require 'space', 'dash', 'single-quote', etc.
Please see this FAQ
Bob
The alpha validation does exactly what it says on the box and not a penny more :-( It is not suitable for most name fields where you may require 'space', 'dash', 'single-quote', etc.
Please see this FAQ
Bob
Thank you Bob. It sounds like I had evaluated the validate-alpha routine correctly.
I looked at the customized client side validation routine & it appears to be worth an investment of time.
As more women are now assuming hyphenated last names after marriage, I think more of this will be seen.
An increasing number of women don't want to change their last name to their husband's last name. It was an old practice in a time when a woman became married, she was considered a man's property. (Owned!) Women don't want to be viewed, seen, considered anyone's personal property or owned any longer! They feel they have tolerated all the abuse their gender never deserved!
They are very strong about it here & raising the devil about keeping their hyphenated names. They are causing MUCH grief for our data entry people! That is rippling through management & I was called upon to make hyphenated last names possible for the sake of the executive's sanity!
Thanks again for the reply. It confirmed my suspicion about the routine.
Roger
I looked at the customized client side validation routine & it appears to be worth an investment of time.
As more women are now assuming hyphenated last names after marriage, I think more of this will be seen.
An increasing number of women don't want to change their last name to their husband's last name. It was an old practice in a time when a woman became married, she was considered a man's property. (Owned!) Women don't want to be viewed, seen, considered anyone's personal property or owned any longer! They feel they have tolerated all the abuse their gender never deserved!
They are very strong about it here & raising the devil about keeping their hyphenated names. They are causing MUCH grief for our data entry people! That is rippling through management & I was called upon to make hyphenated last names possible for the sake of the executive's sanity!
Thanks again for the reply. It confirmed my suspicion about the routine.
Roger
This topic is locked and no more replies can be posted.
