Originally Posted by
username
I think this is not a problem until it is. In recent years with the TSA SSSS validation and APIS, the general rule of thumb is the name must match the passport fully. The other thing to consider is Frequent Flyer program validation name matching.
It seems in the systems, the first and middle names are squeezed together with spaces, dashes and probably apostrophe removed but I guess this is how the technology was programmed in the 1960s.
I would stay if OP does not fix this and is stopped by an agent, the "I have always been able to do this" argument might take a little escalation to be resolved.
- That's not nearly as good an argument as the "your system formatted it this way" argument. Keep this message is simple as possible (i.e. no elaboration).
- The escalation you speak of typically entails the agent making no more than 2 or 3 keystrokes.
- Since you are holding up the line, the agent has an incentive to get you out of his/her hair ASAP.
Switching gears, the main reason I became adamant and consistent about sticking with the SURNAME GIVENNAME format across the board is that not even the most primitive databases can screw this up. Whether or not they split the order, remove letters, or insert special characters, isn't my concern. In the event my names had any apostrophes or mixed case letters, they wouldn't anymore, per my protocol. KISS!