Pet peeve: databases that can't deal with names that don't fit the first-middle-last convention. Newsflash: Less than half of all humans follow that convention. Some of us have no middle name, some have two, many put the family name first. It's ignorant and rude to expect everyone to follow the NW European pattern.
When I made databases, I made the name field free-format, do what you want, we're not gonna use it to identify you anyway. And that was 30 years ago; there's no excuse now.
@ImagineThat There were big issues I encountered with free form names. First was consistency of name entry. Free form let any data entry person decide the format. Then sorting for retrieval matching or reporting lists was problematic. Finally few name databases exist as singular sets: data are exchanged or mapped to other tables. Free form names misses matches and leads to multiple records or missed matches.