On Sat, 26 Feb 2011 22:18:06 +0000 (UTC), [email protected] wrote: >It follows that an indeterminate amount of database structure corruption HAS >been proven, which at least my copy of Legacy 6 CAN NOT DETECT and DOES NOT >REPORT.
You are mis-representing my private emails. You do not appear to have read the last several. The structure of the database appears to be correct. Pointers appear to be pointing where they should point. The problem appears to be that somehow you have extra sets of parents in your database. Note that I said PARENTS, not SPOUSES. >That would appear to make it not user fixable It certainly is fixable by the user. May take a little work but it can be fixed. All you have to do is unlink the extra parents. >and raises the spectre of a general problem which hasn't been reported because >it lurks invisibly in the database. Can't answer that since I don't have access to Legacy's bug reporting system. >It is almost certainly in family files that I have distributed, and likely in >gedcom abstracts which I have passed to other genealogists. Probably. >Dunno if it would propagate if I or they converted the file to Legacy 7 format It probably would since there is structurally nothing wrong with your database. >and still would lurk silently because Legacy 7 doesn't detect it either. There is nothing to "detect". Having multiple sets of parents is a valid situation. You can run "Search > Miscellaneous Searches > Individuals with multiple parents" to find potential problems, but some of these might be valid adoptions, etc. >Another thought is that it's an artifact of, or amplified by, frequent >Intellimerging. I suspect, since that is in the subject line of this thread, that there is a bug in "Intellimerging" (as you call it) which is adding extra sets of parents. Or there is something in the way you are merging that is causing the problem (i.e. a methodology problem). >Legacy 7 work the same way? You can always download the standard version of V7 (but don't overlay V6 when you install it) and give it a test drive. Don't try it on a copy of your database unless you clean up your database first. >Dennis suggests I make a small file and repeat whatever caused this, and I >would if I had any idea what that was. What you should do is create a brand new database and add a handful of people from scratch. Back this up. Then perform the usual Intellishare things you would normally do (writing down the steps). Inspect your merged database and look for multiple parents (not spouses) at every step in the process. When you see an extra set of parents appear, stop and get back to us with the details. Another idea would be to clean up your database and continue business as usual. Then, after every merge, run "Search > Miscellaneous Searches > Individuals with multiple parents" and look for any additional individuals that appear. -- Dennis Kowallek (LTools) http://zippersoftware.com/ltools/index.htm http://groups.yahoo.com/group/ltools P.S. Post in plain text if you want me to read it... 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
