Hi Cathy My case is unusual. I was ((and still am) having a problem with my file. Repair did nothing. support was unable to duplicate it. So I was curious to see if converting it might correct the problem.
So, I did an export to a new file, but still had the problem. So I thought perhaps using GEDcom might correct the problem. I did the export/import but still had the problem. I was just using this method as a tool to diagnose any file differences that might help locate the cause. The good news is that although I still have the problem, I now know that it only occurs with SourceWriter formats, and not with Basic source formats. So I think I am closer to locating a solition. Thanks for oyur help and ideas. Bob Hansen On Jan 17, 2015, at 3:34, Cathy Pinner <[email protected]> wrote: > The question is why did you use a Gedcom to go from Legacy to Legacy? There > is an export to Legacy file - though it doesn't have as many options to > customise the fields, it does transfer all the data. > The only time you'd consider using a gedcom to go from Legacy to Legacy is > when for some reason you are going to an earlier version. > > The SourceWriter sources transfer via Gedcom fine for something that requires > a gedcom - but they transfer as basic sources. > > Cathy > > [email protected] wrote: >> >> Yes. This is normal behaviour, GEDCOMs cannot support any Source >> Writer type of sourcing. >> >> Ron Ferguson. >> >> Sent from my Xperia™ smartphone >> >> Genealogy Bob <[email protected]> wrote: >> >> In trying to solve another problem, I ran into an unexpected issue. >> >> I exported a Legacy 8 file t o GEDCOM, for Legacy use. >> Then I imported the GEDcom file into a new Legacy 8 file. >> I soon discovered in the new file that my Master Sources, that had >> originally been created with SourceWriter, showing the "*" in front >> of the name, no longer displayed the "*", and were behaving like they >> were done with Basic Source tool. >> >> There were a lot of options to select from, did I miss one that allows >> me to keep the SourceWriter formats? If SourceWriter formats will be >> lost, I could not find a mention of that in the Help files, so I think >> that should be added as a caution if this is normal. >> >> *Is this normal behavior when using the GEDcom export/import tools?* >> >> >> >> Legacy User Group guidelines: >> http://www.LegacyFamilyTree.com/Etiquette.asp >> Archived messages after Nov. 21 2009: >> http://www.mail-archive.com/[email protected]/ >> Archived messages from old mail server - before No v. 21 2009: >> http://www.mail-archive.com/[email protected]/ >> Online technical support: http://support.legacyfamilytree.com >> 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/[email protected]/ >> Archived messages from old mail server - before Nov. 21 2009: >> http://www.mail-archive.com/[email protected]/ >> Online technical support: http://support.legacyfamilytree.com >> 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/[email protected]/ Archived messages from old mail server - before Nov. 21 2009: http://www.mail-archive.com/[email protected]/ Online technical support: http://support.legacyfamilytree.com 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
