I have this problem I imported a gedcom to Legacy and because I only needed a little bit of the names in the file I exported a gedcom from that file. When export was done it said I had exported 200 individuals I forget how many families. But when I imported the new gedcom it only had 2 people in the gedcom. I have tried it with several files and it happened with all them. Jerry

I've read JerrSingle's comments about Legacy's GEDCOM with interest. I am a Generations user but because it's company (Sierra, Inc.) is now defunct I decided to switch to Legacy. When I transferred my data from Generations to Legacy I found out many things were not getting into Legacy from Generations, especially sources (and some comments too). I think most of my individuals got there. I contacted Legacy Customer Service and they sounded very helpful. She said lots of former Generations users were having trouble with GEDCOM transfers to Legacy, implying that Generations was at fault. Sources were out of kilter or just not there. She told me to e-mail my GEDCOM file and that "Dave" would take a look at it. That was SIX MONTHS ago. I've e-mailed several times but no response. Legacy isn't as enthusiastic about helping me now. I now suspect that Legacy's GEDCOM import algorithm is wrong. I've looked at my Generations GEDCOM file and, while I'm not a GEDCOM expert, it looks to me like sources are in there correctly (i.e. sources are all at the end and look like this: @S22@... for example). JerrSingle, I think Legacy has a big GEDCOM problem -- Dan JerrSingle@aol.com wrote: >I have this problem I imported a gedcom to Legacy and because I only needed >a little bit of the names in the file I exported a gedcom from that file. When > export was done it said I had exported 200 individuals I forget how many >families. But when I imported the new gedcom it only had 2 people in the >gedcom. >I have tried it with several files and it happened with all them. >Jerry > > >==== LEGACY Mailing List ==== >To contact the list administrator, or to unsubscribe, or to view the >list archive, or for other list information, go to the web page at >http://lists.rootsweb.com/index/other/Software/LEGACY.html > >============================== >New! Family Tree Maker 2005. Build your tree and search for your ancestors at the same time. Share your tree with family and friends. Learn more: http://landing.ancestry.com/familytreemaker/2005/tour.aspx?sourceid=14599&targetid=5429 > > >

Dan, I last responded to you about this back in October - sorry if you never got the final "verdict" from Dave on the Source problem. One of the big problems with a Generations gedcom comes about when a user has selected to do "FreeForm" sources. Since those sources aren't formatted in the standard way in Generations and they're exported with a TEXT tag, the only way Legacy can import that is into the Text of Source field in the Source, with the Source List Name as "Source". There's nothing that we can do with that style of source other than to import it into the Text field. A correctly exported source would be seen in the gedcom as: 0 @S22@ SOUR 1 _MEDI Directory 1 ABBR Washington, Spokane, Spokane - 1907 - Spokane City Directory 1 TITL Spokane, Washington City Directory, 1907 1 AUTH Research Publications, Inc. 1 PUBL New Haven, Connecticut: Research Publications 1 REPO @R10@ 0 @S24@ SOUR 1 _MEDI Directory 1 ABBR Washington, Spokane, Spokane - 1908 - Spokane City Directory 1 TITL Spokane, Washington City Directory, 1908 1 AUTH Research Publications, Inc. 1 PUBL New Haven, Connecticut: Research Publications Whereas the FreeForm sources from Generations show up as: 0 @S64@ SOUR 1 TEXT Missouri State Archives, Birth & Death Records 0 @S65@ SOUR 1 TEXT From Letta May Miller-Reilly; written lists, a family Bible and 1 TEXT a scrapbook of newspaper clippings; about 1970 With the first set of sources, Legacy knows *exactly* which fields the various elements of the source should be placed. Legacy has placed the TEXT tag into the Text of Source field, the only option an import by any program would have (other than to ignore it completely, which some programs do) The workaround that we've been giving Legacy users, besides manually editing all the FreeForm sources to a standard format either before or after export, is to go to Options > Customize > Sources and select to Include Master Source Text on Reports. That way the sources will show up on the reports for you until they can be reformatted by the user to a standard source format. The other problems we've seen with Generations exports can be dealt with and Dave is working on them as they come up. Thanks for using Legacy. Sherry Customer Support Millennia Corporation Support@MillenniaCorp.com http://www.LegacyFamilyTree.com We are changing the world of genealogy! When replying to this message, please include all previous correspondence. Thanks. -----Original Message----- From: DanBCooley [mailto:dbcooley@rcn.com] Sent: Monday, January 17, 2005 2:26 PM To: LEGACY-L@rootsweb.com Subject: Re: [LEGACY] Importing and exporting Gedcom problems I've read JerrSingle's comments about Legacy's GEDCOM with interest. I am a Generations user but because it's company (Sierra, Inc.) is now defunct I decided to switch to Legacy. When I transferred my data from Generations to Legacy I found out many things were not getting into Legacy from Generations, especially sources (and some comments too). I think most of my individuals got there. I contacted Legacy Customer Service and they sounded very helpful. She said lots of former Generations users were having trouble with GEDCOM transfers to Legacy, implying that Generations was at fault. Sources were out of kilter or just not there. She told me to e-mail my GEDCOM file and that "Dave" would take a look at it. That was SIX MONTHS ago. I've e-mailed several times but no response. Legacy isn't as enthusiastic about helping me now. I now suspect that Legacy's GEDCOM import algorithm is wrong. I've looked at my Generations GEDCOM file and, while I'm not a GEDCOM expert, it looks to me like sources are in there correctly (i.e. sources are all at the end and look like this: @S22@... for example). JerrSingle, I think Legacy has a big GEDCOM problem -- Dan

Jerry, You can open a gedcom in a text editor program such as Notepad or Wordpad. Open it up and take a look to see if everyone you wanted to export actually were included in the gedcom. Just look for the names - you don't need to worry about all the other information in there. Thanks for using Legacy. Sherry Customer Support Millennia Corporation Support@MillenniaCorp.com http://www.LegacyFamilyTree.com We are changing the world of genealogy! When replying to this message, please include all previous correspondence. Thanks. -----Original Message----- From: JerrSingle@aol.com [mailto:JerrSingle@aol.com] Sent: Monday, January 17, 2005 5:21 AM To: LEGACY-L@rootsweb.com Subject: [LEGACY] Importing and exporting Gedcom problems I have this problem I imported a gedcom to Legacy and because I only needed a little bit of the names in the file I exported a gedcom from that file. When export was done it said I had exported 200 individuals I forget how many families. But when I imported the new gedcom it only had 2 people in the gedcom. I have tried it with several files and it happened with all them. Jerry

On 17 Jan 2005 JerrSingle@aol.com wrote: > I imported a gedcom to Legacy and because I only needed a little bit > of the names in the file I exported a gedcom from that file. When > export was done it said I had exported 200 individuals I forget how > many families. But when I imported the new gedcom it only had 2 > people in the gedcom. I have tried it with several files and it > happened with all them. I'm not sure what you are trying to accomplish or exactly what you did, so in order to help figure this out please provide answers to these questions. . . . The Gedcom you imported to Legacy went where -- a new (empty) file or one that already contained some individuals? When done did the Legacy file contain all you expected? So then you exported from Legacy to a new Gedcom -- did you want to export everyone or was this a subset? If a subset what method did you use to select the individuals to export? Legacy said it exported 200 into the Gedcom but another program reading that said there were only 2. So you need to see how many were in that Gedcom to see where the problem resides -- did you look? Gedcoms are simply text files and can be viewed using any text editor such as Notepad, Wordpad or even your word processor. You could also go through another Legacy import with the newly-created Gedcom and see how many individuals Legacy says are in it. Repeat the process and look at the Gedcom to see what's in it -- the difference between 2 and 200 will be very evident! Please let us know what you are trying to accomplish with these gyrations -- I suspect there could be an easier way. Cheers, -- Dave N. -- David Naylor, Halton Hills, Ontario, Canada. ---