On 10 Sep 2015 at 16:42, Cathy Pinner wrote:
> Steve,
>
> On the import Gedcom screen check Try to keep original ID numbers
> AND
> uncheck Fill all existing abandoned RINs/MRINs
>
> Also make sure that the existing Legacy file doesn't have any RINs in
> the range you are importing or the RIN can'
Steve,
On the import Gedcom screen check Try to keep original ID numbers
AND
uncheck Fill all existing abandoned RINs/MRINs
Also make sure that the existing Legacy file doesn't have any RINs in
the range you are importing or the RIN can't be kept.
My first genealogy program was one called "Famil
On 22 Aug 2015 at 6:41, Sherry/Support wrote:
> We have an extensive article "File Import and Clean Up" in our
> Knowledge Base at
> http://support.legacyfamilytree.com/article/AA-00922
I have a somewhat different problem with importing GEDCOM files which is not
covered by that article.
At the m
We have an extensive article "File Import and Clean Up" in our
Knowledge Base at
http://support.legacyfamilytree.com/article/AA-00922
The Knowledge Base can be accessed by clicking on the Tips from the
Experts link in the Support section of the Legacy Home tab or by going
to www.LegacyFamilyTree.c
Hi Les,
Excellent Advice.
I suggest you add - check all Master Lists. View - Master Lists
Some of your clean up tasks are easier and more efficient in the Master
List.
I would also add the Gedcom as a source to every item in the database.
This can be done easily when you are importing the file to
I'm sure many, if not most of us, will have imported a GEDCOM and regretted
not "making it clean" before entering it into our master Legacy file. I
decided to compile a set of notes/instructions to ensure that all my future
downloads were "cleansed" in a full fashion. Here is a copy of my
notes/ins
6 matches
Mail list logo
