When saving census records today, the location field is presenting double spaces, ie, Indianapolis,spacespaceMarionCounty,spacespaceIndiana.

Spaces are also being added to existing location records (birth,death).

This is occurring in all place fields after all commas when 'saving' the link to an Ancestry.com extract from whatever type of actual record.

The save screen, with data entered for vital dates, puts double spacing after every comma in a place field, regardless how that place entry got there (keyed in by Tree user or from the extract by Ancestry.com).

This is adversely affecting the type-ahead fields when keying in new data as well.

The Weekend Gremlin started early this week.

Drat!

I thought they took him to New York to ring the NYSE bell this morning!

;)

If so, he missed the opening at NASDAQ, where ACOM now trades.

Ahhhh... so *that's* why he didn't show up.

;)

They might've. This double-space routine started a few days ago, obviously a dandy new piece of self-executing code.

Not a one-time deal like making Census images or entire databases disappear.

There seems to be a special gremlin who thinks stuff up over the weekend and installs it on Mondays.

Also somebody's been wonking around with the Search Engine. Tree Hints are getting lots less relevant. Like for people not with same first name, nowhere near same birth-year, nowhere near same birth-state, etc.

Attention whoever on staff is doing this, in WV the given name 'Icie' is short for 'Isophene' and is **not** the same name as 'Essie.' 'Sena' and 'Cena' are short for 'Aseneth', and quite unrelated to Serena, Lena, and Celia. Heheheheh.

[QUOTE]

Attention whoever on staff is doing this, in WV the given name 'Icie' is short for 'Isophene' and is **not** the same name as 'Essie.' 'Sena' and 'Cena' are short for 'Aseneth', and quite unrelated to Serena, Lena, and Celia.
[END QUOTE]

You should send this to Anne Mitchell so that , hopefully, she can get it input to the "Name Authority".

Re: e mail message from Kenny Freestone-this issue will be fixed next Monday. My question to him: Why isn't there some oversight to these programmers who change code willy-nilly without checking to see just what they are doing. Are there any consequences and does anyone at Ancestry even care. Looks like they depend on us-the poor users who are at their mercy-to find and report the nutty things they do. Maybe a game to see how many people recognize something has been messed up??? Do they keep score!!!

I really think I'd be more interested in Kenny's answers to your questions than a date as to when it will be fixed!
*GRIN*

I can live with wonky tree hints since I never connect them and only have to look at them to make the stupid leaf go away. Wish there was a way to not accept without having to look at the dern things.

I'd much rather they work on fixing misspelt and nonexistent place names in sundry databases, which are a much wider searching problem. E.g., searching for X surname in Worcester Co, MA will not bring up the results that are indexed as being for Worb, MA; for Y in Worcester Co., MD will not bring up the reults that are indexed as for Worchester Co, MD; for Z in Somerset Co, ME will not bring up the results that are indexed as for Somersetshire, ME.