It's not just you, there is a whole slew of BS that women with hyphenated names--or at least women like me who had an actual credit history before marriage--have to go through that no one else does. Like NONE of my old credit cards are willing to let me change my official name to my ACTUAL name. The phone company won't let me change my name on the billing for the phone. My health insurance won't let me change my name either. Social security was kind enough to deign to let me use my new name, but they--swear to God--screwed up my official birthdate on their paperwork (a transcription error) and now we need to use the WRONG BIRTHDATE on our taxes or they will be rejected by the IRS. It's all very minor but it really bugs.
I haven't had trouble with banks or my debit cards, but I have been yelled at by the lady at the dry cleaners. And all of my medical records are either under my maiden name or under my name without the hyphen in one big long name because their computer programs will not allow for hyphens. This makes calling any doctor's office (which is something I do often) and actually having them find my file a big huge pain in the ass.
I'm all for people being able to use any names they choose for themselves.
However, I know for a fact that hyphenated or even particularly long names can be problematic for any number of systems. Last name fields are often limited to a certain number of characters. And sometimes hyphens aren't recognized in an alpha field or they come out funky when you download or output the data. Stuff like that, even before you try to label somebody's personnel file and have to shrink it down to 8 pt type.
Like, my first search on the subject turned up Don't use hyphens in your database names.
"Better to stick to lower case column names consisting only of alphanumeric characters and the underscore character (MySQL column names cannot begin with a digit 0-9). This will make your MySQL project more portable across operating systems and system configurations. Even if it is legal to use the hyphen character in a MySQL database name or table name, avoid doing so as it will eventually cause problems (if a PHP script treats it as a minus sign when processing code, and you end up wasting hours trying to figure out what's wrong)."
This makes calling any doctor's office (which is something I do often) and actually having them find my file a big huge pain in the ass.
Yeah, that too. Honestly, women have been hyphenating their names for decades, it's not a new phenomenon. If society wanted to catch up with the times, it could. It's just resistance. Like I said, in my case I think part of the problem is that we did the "unusual" thing of putting DH on my accounts rather than the other way around. Because Name #2 has a lot more leeway than the original name on the account.
Don't use hyphens in your database names.
Like I said, if society (in this case database programers) wanted to catch up, they could.
Like I said, if society (in this case database programers) wanted to catch up, they could.
This. I had no idea what I was getting into with the hyphenating. Like you said, women have been hyphenating names for a few decades now, so I really didn't expect it to be a big deal.
Here's a gripe from a medical office, which gives you a sense of the issue on the data tracking side:
********
If there's one thing that annoys me, it's women who hyphenate their names. I'm a doctor and as such must create charts which are then filed away in alphabetical order.
So Mrs. Jayne Gorden-Vangeroffson comes in for an exam. She writes her name on my form as Jayne Gorden-Vangeroffson. So we file her chart this way and then attempt to file her insurance.
But her vision plan has her listed as Jayne Vangeroffson and so the claim is denied. After several hours on the phone, my staff finally gets ahold of someone and they resolve the issue.
Then she gets pink eye and comes in for that. She identifies herself as Mrs. Vangeroffson this day. (When filing a hyphenated name, you're supposed to go by the first name of the two so she'd be filed under "G") My staff spends a long time looking all over the place but can't find her chart. We question her repeatedly about the file being listed under any other name, but she denies this and since she's been married for over ten years. Finally, we ask her if perhaps she hyphenated her name? Oh yeah, I think I did. So we finally find the chart right where it should have been.
I treat her and then try to file her medical insurance. Remembering the previous problem, we file under Jayne Vangeroffson. But her medical insurance has her as Jayne Gorden. More staff time wasted!!!!!!!
Please women, do not hyphenate your name. You will be creating nothing but problems for yourself and anyone who must deal with you. Doctors will not be able to find your chart. Insurance companies will not have you listed as a client. The list goes on.
If you want to keep your maiden name, keep it. Just tack the new name on at the end without a hyphen. Who gives a fuck if you have three or four names?
But please, no more hyphenated names!!!!!!!
There's all sorts of stuff that can screw up names in databases. The university system runs into some minor problems with names with any kind of punctuation, so I always have to be careful entering grades for any class that has a D'Angelo or O'Malley or anything else that like in it, because different parts of the computer system will have them alphabetized differently, so I can't just copy and paste the list of grades like I can for other classes. Although, I almost never copy and paste anymore, because lately, just about every class has had at least one kid with a name that the system did something weird with.
My name is so often misspelled doctors don't find my chart anyway(people leave the H out)
It's interesting looking through some of the replies to these complaints.
One person simply notes that in Finland the SS# equivalent is the key and that's all that matters.
Another person responded to a complaint on the subject by saying:
Personally, I think it's disrespectful to a person to write his/her name as anything other than the way that person want's to see it. Smithbarney is not the same as Smith-Barney. If I was Mr. Smith-Barney and received a letter with my name improperly spelled like that I would not be favorably inclined towards whatever the letter was about.
You state that you are using 'Title Case' (StrConv I assume). Are you concerned with names like O'Brien and Smith-Barney being improperly capitalized as O'brien and Smith-barney? It's no problem to write a User Defined function to check for a hyphen within a name and capitalize the next character if that is your concern. A table of name exceptions does well with names like O'Brien (as well as McDonald and van den Steen).
Another notes that hyphenated names and multiple names are common in other parts of the world saying...
********
You people need to crawl out of our little American ghetto and go visit the other 90% of the world sometime to get some perspective. Hyphenated names are extremely common.
But what's also common is dual surnames that are not hyphenated. And they are not just for women. In Spain it's quite normal for a man to use both his father's and mother's surname--and the father's comes first. This is less common but nonetheless quite proper in most Spanish-speaking countries.
Sometimes they will write their name as Enrique Meseguer y Correa, sometimes as Enrique Meseguer-Correa. But you're just as likely to see it as Enrique Meseguer Correa. You're expected to know that Meseguer is a surname, not a Christian name. (They don't name their children Madison and Taylor like we do. Those are last names.) So you'd better not commit the faux pas of calling him Mister Correa! It's okay in informal speech to use only one surname, but its the father's name, the first one.
Arguably the most famous Spanish language writer in the world (actually one of the four or five most famous writers period, the sun is setting on English literature) is Colombian Nobel laureate Gabriel García Márquez. American newscasters continue to refer to him as Mister Márquez. That may have been okay fifty years ago when it was presumed that America was the center of the universe and we couldn't possibly be expected to master the conventions of other cultures, but it isn't okay any more.
Anyway, it's up to us computer people to make our stupid barely-functional virus-friendly user-hostile software conform to the real world, not vice versa. Millions of people have hyphenated names and it's not an affectation. It's reality. Software developers had better pull their heads out of their X-Boxes and pay attention.
It just isn't that difficult for a program to be designed to find Suzie Smith-Jones and Suzie Baker-Smith if you type in Suzie Smith, Suzie Jones, Suzie Baker, Suzie Jones-Smith, Suzie Smith-Baker, or Suzie Smith-Jones-Baker-Washington. It's called "requirements definition" and it's something that American software developers are proudly ignorant of. Draw a flowchart on the back of your Starbucks napkin then run back to your cubicle and start coding. Nonetheless, in places like Los Angeles County, where there are millions of people from other countries whose naming conventions are different, the municipal government software has no trouble finding people's records if they turn up in a public school, hospital, or sheriff's office, no matter how the clerk enters it. Computers are supposed to make stuff like that easy!
If you're software is so dysfunctional that it can't find something this easy, you should send it back for a refund. Or shoot the idiot programmer.