Forum Discussion
- MarkShnier__YouQrew Legendtry
NotLeft([Full Name], " ")
It will be better but you will still have issues because you may have data with a middle name or initial like
Michael J. Fox
------------------------------
Mark Shnier (Your Quickbase Coach)
mark.shnier@gmail.com
------------------------------- TroyMacPhersonQrew Cadet
Thanks Mark, I'll try that.
You're right, some of my Full Name entries have 3-4 names...
------------------------------
Troy MacPherson
------------------------------- JohnCroslandQrew TraineeI would recommend using the Length and Part formulas. So, it would be something like If(Length(Part([Name], 4, " "))>2, Part([Name], 4 " "), Length(Part([Name], 3, " "))>2, Part([Name], 3, " "), Part([Name], 2, " "))
------------------------------
John Crosland
------------------------------
- rbuschmeyerQrew TraineeSo an interesting question is "what is the nature of input" of the Full Name field? Is that a user-input field? If so, (and if it is possible in your scenario), it might be easier to normalize the data through a different user-input strategy (e.g. different fields for each name component).
Seems the parsing of the last name could be extremely problematic given you could have several different styles of ethnic naming.
Sorry if I'm not providing an acceptable solution...just some thoughts.
------------------------------
Ryan Buschmeyer
------------------------------- JeffPeterson1Qrew CaptainThat's what I was thinking also. This is why on many forms, first, last, middle and suffix are separate fields.
------------------------------
Jeff Peterson
------------------------------
- SimonHQrew Cadetanytime a question about names comes up, these articles come to mind
https://www.kalzumeus.com/2010/06/17/falsehoods-programmers-believe-about-names/
And perhaps the most famous XKCD
https://xkcd.com/327/
------------------------------
Simon H
------------------------------