I've gone to the help file on this one. The process they outline is to import all data into one family file. I was merging from one into another. They make a statement that when merging the right into the left, that the right is deleted. This is fine when merging duplicates in a single file, but not at all good when pulling in from a separate file. I believe that is the cause of loosing data. Now I know, and won't make that mistake again. Even so, I don't believe software should allow me to mess up my source without so much as a warning. If it is not recommended to merge from one fine into another, then the software shouldn't allow me to do so or, at the very least, explain the dangers before proceeding.
On Mon, Jan 10, 2011 at 12:26 PM, James Cook <[email protected]> wrote: > I expect loss of data via GEDCOM. What I did not expect is to export > a GEDCOM and have date removed from my master file. Or, to merge into > a new family file and have data removed from the master file. I did > not want or expect any edits to the master file, that is why I created > a new one to merge into. I do not understand why this happened. > > My question here is specifically why did my master file get corrupted? > My understanding is that I was making edits to a completely separate > file and only pulling data in from the original. I did not ever see > an option that was to pull the data in and then delete from the > source!?!?!?!?! > > > If this is how the merge works, then I'll not be using it again either. 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://www.LegacyFamilyTree.com/Help.asp To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp
