Glad that it worked. There is often (not always) a workaround to be found.


Paul



From: Robert Stewart [mailto:trawetstre...@gmail.com]
Sent: April-09-14 12:43 PM
To: legacyusergroup@LegacyUsers.com
Subject: RE: [LegacyUG] Bad TITL import



Thanks Paul.



A solution that worked.



In fact, after I renamed 1 TITL to 1 TITX in the gedcom, performed the import, 
it actually let me assign it to a Title (!) in the program (and not create an 
event).  It imported perfectly.  I found a TITX in the tag list, and a quick 
edit  it’s now Title.  And I’m back down to a reasonable amount (113) of tags.



Thanks for the solution!



Robert



From: Paul Gray [mailto:graypa...@outlook.com]
Sent: Wednesday, April 9, 2014 12:52 PM
To: legacyusergroup@LegacyUsers.com
Subject: RE: [LegacyUG] Bad TITL import



Hi again Robert,



It’s clear that Legacy isn’t handling TITL the same as Roots Magic. In fact, 
standard Legacy doesn’t seem to have a ‘Title’ fact as RM does. I’m not going 
to debate which is right and which is wrong, the simple fact of the matter is 
that each program has their own data structures and imports and exports data as 
they best see fit, and inconsistencies occur.



However, you need a solution, not a debate. I may have found one. This was my 
workaround test.







1.      In RM, I added a Title (Nobility) fact (which seems to be a RM standard 
fact) to myself. I am guessing this is the RM fact type you used.



2.      Exported Gedcom



3.      Used a text editor (Notepad) to view/modify the GEDCOM to change the 
TITL tag to TITX. That changes it from a tag that Legacy recognizes and 
processes in a way you don’t want, to an unrecognized tag.



4.      Imported modified GEDCOM into Legacy.



5.      After the first step (analysis) you will see a popup saying there are 
unrecognized items. Click Yes to review them. TITX will be in the box at the 
upper left. Click ‘Create an Event for this Tag’, Enter ‘Title’ or whatever you 
want, and proceed. Seemed to work for me and created a ‘Title’ event with 
description, date, and place.



The only thing that’s a bit limiting about this is you seem to need to create a 
new event. I couldn’t seem to map to an existing event type.



Perhaps this is a solution for you?



Paul












Legacy User Group guidelines:
http://www.LegacyFamilyTree.com/Etiquette.asp
Archived messages after Nov. 21 2009:
http://www.mail-archive.com/legacyusergroup@legacyusers.com/
Archived messages from old mail server - before Nov. 21 2009:
http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/
Online technical support: http://www.LegacyFamilyTree.com/Help.asp
Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) and on our 
blog (http://news.LegacyFamilyTree.com).
To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp

Reply via email to