Steve,
From my own sad experience, I know that the place names in the Master
Location List are vulnerable to mistakes you make when you combine
locations there. You should/must always make a backup of your data
before making any changes to location names while in the Master List.
The Legacy program does not change location names on it's own. If you
have a recent backup, my advice is that you speedily restore it. You
can give the restored file a different name, and compare the Master
Location List of the two files. This might help you feel assured
concerning the integrity of the program. If the backup is not a recent
one, you can nevertheless use the restored file to see which records had
Colchester and which had St. Luke's, and make changes as needed.
Joseph Leavitt
On 4/1/2016 1:27 AM, Steve Hayes wrote:
This morning I discovered that Legacy had changed one place name to another,
without my knowledge.
I was checking a marriage, and found that my place for the marriage was St
Luke's, Middlesex, England, while the source I was checking said Colchester,
Essex, England.
I changed the place name to Colchester, but kept getting another place, and
then discovered that Colchester had disappeared from the Master Location
List, and that in every instance Colchester, Essex, England had been changed
to St Luke's, Middlesex, England.
I had about 1000 people who use Colchester, but very few who used St Luke's,
so I simply edited the place name to change it to St Lukes, but my concern is
-- how many other place names in the Master Location List is Legacy changing
without my knowledge?
--
_______________________________________________
LegacyUserGroup mailing list
[email protected]
To manage your subscription and unsubscribe
http://legacyusers.com/mailman/listinfo/legacyusergroup_legacyusers.com
