Bill,
I was commenting on one known origin of Individual # not found errors.
Hinting sometimes causes these as Hint results are returned after
a) you've changed file or
b) you've merged or deleted the person.
Most of these problems have been fixed but we had a lot at one time
pre-release. They're still being seen sometimes but now are difficult to
reproduce and so difficult to know whether it is still hinting sometimes
causing them or other things.
Cathy
Billy Mittelstadt Jr <mailto:bmittelstad...@gmail.com>
Friday, 21 July 2017 10:17 AM
Cathy,
I'm curious. The only hint being used is family search. Why would
cause it to crash?
BTW did the check/repair immediately and then backed up the file.
Thanks.
Bill
On July 20, 2017, at 12:47 AM, Cathy Pinner <genea...@gmail.com> wrote:
Bill,
If you restore a backup file, do run a check/repair on it straight away.
A Legacy backup zip preserves your database as it is.
You only lose SourceWriter sources if you use a Gedcom. Gedcom is not
the way to backup your Legacy file as a normal rule.
Error 3021 has been around from time to time since I began using Legacy
in 1998. It has various causes and a check/repair normally fixes it but
not always.
These "individual not found" errors are relatively new. Some relate to
hinting.
It could be a good idea to turn hinting off when doing merges.
If you keep getting errors, contact Support.
Cathy
--
LegacyUserGroup mailing list
LegacyUserGroup@legacyusers.com
To manage your subscription and unsubscribe
http://legacyusers.com/mailman/listinfo/legacyusergroup_legacyusers.com
Archives at:
http://www.mail-archive.com/legacyusergroup@legacyusers.com/
