The extent of "Mess" is purely, I have found, a function of the file sizes involved and the length of time the import runs before the error is triggered. In the first go round of 3021 errors that produced similar results, the errors created merging two small files were confined to the few existing individuals and marriages. When the same error occurred in my main, 97,000+ file and a second large file and the import ran nearly to completion, the mess spread all over the place, with little rhyme or reason, sometimes producing cascade effects., ie sex changes following created marriage leading to further sex changes in the actual marriage, etc. The RIN numbers involved might start with 12, jump to 1769, then 32910, and so on. My record was 23 pages of changes, all imaginary.
Wm Voss -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Michel Lacoursiere Sent: Monday, 08 July, 2002 17:47 To: [EMAIL PROTECTED] Subject: Re: [LegacyUG] Double Spouse references > Close, but not exactly - actually 3020. Ok! I got it. > I can import the whole file without > the error, but not just a certain focus group (a person and ancestors - > works if ltd to 10 gens, but not with all gens option [and this person only > has about 10 gens]) - works when importing from a different database, so I > think maybe that particular database that I was trying to import from has > problems. Your file is probably fine. I can reproduce with different files and with various number of generations. What I can not reproduce is the "mess" that you say you had after the import was cancelled. To unsubscribe please visit: http://www.legacyfamilytree.com/LegacyLists.asp Legacy User Group Etiquette guidelines can be found at: http://www.LegacyFamilyTree.com/Etiquette.asp To unsubscribe please visit: http://www.legacyfamilytree.com/LegacyLists.asp Legacy User Group Etiquette guidelines can be found at: http://www.LegacyFamilyTree.com/Etiquette.asp
