Thanks Brett. I think I will wait and see how well the direct import works that Ken McGinnis says they are working on.
I just hope it isn't to long before it is released. After trying a GEDCOM I did a repair and got an error on the file. Dale On 9/17/2014 4:13 AM, Brett McL Robinson wrote: > Hi Dale > > Further to Wendy, many years ago I went through a difficult move to > Legacy. My suggestions for any difficult gedcom transfer where you need > to get hands-on: > > 1 Do what you can to get the data across with mapping the fields > during the export/import process (customising where data in the source > goes in the target for the non-standard fields). > > 2 If necessary set up test files with the field name entered as the > text in the respective field in the test files, so that it is clear > where the data is going from and to. Do this for both the source and the > target software > > 3 Open a test gedcom from both the source software and the target > software to find out what codes are used for the fields. Open the > gedcoms in a text editor (eg Notepad or Word) to see the structure. > > 4 If necessary you can use find-and-replace in the text editor to > change the field names so that the gedcom process gives you the correct > results. This is simple if the fields are to change directly from one > code to another, or to combine several into one. However it can also be > done one item at a time if you want to split a source field code into > two in the target software (you need to tap "yes" or "no" for every item > as the find-and-replace progresses, but you don't enter any new data). > > > Cheers, Brett > > On 24/08/2014 11:13 a.m., Wendy Howard wrote: >> Hi Dale, >> >> ... >> >> Something else to consider - is your database small enough that >> re-typing all your data from scratch is feasible? It might be that >> taking such a close look at it all will lead you to new discoveries, and >> perhaps weeding out mistakes that had been made before. I'd consider >> doing that if it were only a few hundred or a thousand people (I'm a >> quick typist), but not if I were looking at tens or hundreds of >> thousands or more. Only you can answer that, knowing what's in your >> database already and your own skills. >> >> Hope this helps. :-) >> >> Wendy >> >> Dale E O'Connor said the following on 24/08/2014 06:49: >>> I have TMG 7.04 and Windows 7. >>> >>> Do you have any tips on settings for GEDCOM export/import? >>> >>> Did you loose any data? How did you get the data that was lost from TMG >>> to Legacy? >>> >>> Is there anything else I need to look for? >>> >>> Can you point me to a website that already has instructions on switching? >>> >>> Since most people on this list want be interested in this topic you can >>> reply off list. >>> >>> Thanks in advance, >>> >>> Dale >>> > > > > 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 > > > > 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
