Good morning Russ,
I removed Boston from my online tree and re-synced. When I change place names from FTM, the resulting sync times are a factor of 10 times longer than if I make the change in the online tree. Plus, the change does not show up in the online tree. That's an on-going battle with tech support - 3 months and counting.
This is the family of my grandmother, who, along with her younger sister, was born in Boston. The family only lived in Boston for about 5 years, between 1892 and 1896, so there is no census linked to Boston for this family.
I do have my great-grandfather in several City Directories in Boston during that time, and his data also displays as "Louisiana, USA," once I add the county to the original information supplied by the city directories.
Thanks,
Ann
Edit: I just tested removing the comma between Massachusetts and USA, and the combination is interpreted correctly by FTM. But, again, I don't have to do that with any other city, county, state combination.
I removed Boston from my online tree and re-synced. When I change place names from FTM, the resulting sync times are a factor of 10 times longer than if I make the change in the online tree. Plus, the change does not show up in the online tree. That's an on-going battle with tech support - 3 months and counting.
This is the family of my grandmother, who, along with her younger sister, was born in Boston. The family only lived in Boston for about 5 years, between 1892 and 1896, so there is no census linked to Boston for this family.
I do have my great-grandfather in several City Directories in Boston during that time, and his data also displays as "Louisiana, USA," once I add the county to the original information supplied by the city directories.
Thanks,
Ann
Edit: I just tested removing the comma between Massachusetts and USA, and the combination is interpreted correctly by FTM. But, again, I don't have to do that with any other city, county, state combination.