ShariPDX wrote, "It's really a glitch in the Ancestry.com's software that they still haven't dealt with."
No, it's really NOT a glitch or a software problem. I promise. So don't feel badly because ancestry.com hasn't "fixed" it. They have other challenges that DO need fixing, but this isn't one of them.
No, it's not ancestry.com's problem or fault at all; it's OURS.
We just have to learn (some of us the hard way) to slow down and pay closer attention. This "Y, Somme, Picardie, France" thing is 100% due to carelessness on the part of those of us who accept drop-down suggestions too quickly without noticing or thinking about it.
Building a family tree isn't supposed to be a data-entry race. And as helpful as it usually is, the ancestry software only offers suggestions; it doesn't, for example, default to the "Y, Somme" answer. WE have to make that mistake by letting a wrong suggestion STAY there without noticing and rejecting it. I did it way too many times myself and am STILL making corrections. My bad...
Those mistakes DO add comic relief though, like the one that has Roman Emperor Constantine (my 44th GGF) supposedly managing to get himself born in "Superior, Dickinson, Iowa", another common mistake found on ancestry trees. All due to accepting unlikely or downright bizarre drop-down suggestions as facts.
Seriously, though, folks, we really gotta take it slower and more carefully or we'll have a whole FOREST of family trees that look like something out of Dr. Seuss....