On the contrary. With respect, Sven-Ove's statement has nothing to do with the problem being reported.
The problem (as we now understand it) is that Legacy is now corrupting text data during File->import->Legacy file..., with the result that Intellishare fails on 6.0 and V5-latest. Ed On Sun, 2005-09-11 at 18:48, Jeremy Main wrote: > Exactly, > Said much more succinctly than my earlier post > .../Jeremy > > -----Original Message----- > From: Sven-Ove Westberg <[EMAIL PROTECTED]> > Sent: Sep 11, 2005 7:21 PM > To: [email protected] > Subject: Re: [LegacyUG] Intellishare fails on 6.0 and V5-latest. > > > A good program should have flags on how to handle white space. > Eg. > 1) Compare byte by byte. > 2) Ignore trailing white space on lines > 3) One or more white space characters is compared as 1 white space > > > Sven-Ove. > > At 03:50 PM 9/11/2005, you wrote: > >Yes, of course -- stupid of me. I retested and can confirm your > >theory on the tab to space conversion. This is undoubtedly causing > >the other reported problems with editing. > > > >This may prove a nasty one to repair -- how will the program > >distinguish between what really was three spaces and what got > >converted from a tab? Folks might be in for a mess of manual labor. > > > >Wm Voss > > > >Jeremy Main wrote: > > > >>Hi Ed: > >> I believe the problem you are seeing is happening as part of the > >> import and is not an Intellishare/IntelliMerge issue, per se. > >> > >> I've been looking at RIN # 1793 (Benjamin Robertson III) in your > >> original database. I imported a copy into itself and got the 89 > >> individuals it says it was 'not able to merge' > >> > >> What I've found so far is that the General Notes of both the > >> original and the copy contains 112 lines. However, the original > >> has 5,321 characters and the copy has 5,345. So, there IS a > >> difference after import which IntellPass Merge is detecting. > >> > >> However, the difference is that the original has 132 tabs versus > >> 120 in the copy/import (12 fewer in the copy). And the original > >> has 847 spaces versus 883 in the copy/import (36 more in the > >> copy). For a net difference of 24 characters. (5,345 - 5,321 = 24 ). > >> > >> So....... > >>1) The import is changing SOME of the Tab characters to spaces, and > >>2) IntelliPass Merge is considering these tab/space differences > >>significant. > >> > >>I don't think you have a corrupt file. Only that the import is > >>making some unexpected changes. I'll look a littler further and > >>tell you exactly which lines are the ones being changed. Wm's > >>utilitiy, UltraEdit, is probably not considering these differences > >>to be significant. A visual scan can see no difference. > >> > >>.../Jeremy > >> > >>-----Original Message----- > >>From: Ed Barnard <[EMAIL PROTECTED]> > >>Sent: Sep 11, 2005 5:06 PM > >>To: [email protected] > >>Subject: Re: [LegacyUG] Intellishare fails on 6.0 and V5-latest. > >> > >>Ron, Henry, Wm, > >> > >>Thanks for the suggestions! > >> > >>I've been investigating myself, as well. It now appears to me that I > >>have a corrupted database, as someone suggested. The corruption dates > >>back to prior to the conversion to the new format, but didn't manifest > >>itself until after the conversion. > >> > >>Here's what I've tried. (Hopefully Sherry will see this!) > >> > >>I went back to a July backup, ~4000 names, same problem. That is, I > >>restored from backup, converted to new format, closed, made a copy, > >>merged the two copies, got spurious differences in the notes. > >> > >>Same with a May backup of ~450 names. > >> > >>Early May backup of ~150 names didn't fail; nor did a March backup of > >>~120 names. > >> > >>I took the latest master db from my genealogy partner (we always do ftp > >>transfers, which should have integrity checking) and followed Ron's > >>suggestion: > >> > >>I opened the file, did check/repair, did control-b backup, closed, > >>restored from that backup, saved, made a copy, imported the copy, got > >>spurious differences on the merge - but only about 20 differences this > >>time. > >> > >>Meanwhile, I have a completely different database (different family) > >>which I've not touched since May 9th 2005. I merged two copies, it did > >>merge without any differences. So, yes, the problem may well be specific > >>to the one database. > >> > >>Sherry, when Millenia's able to take a look, please let me know, and > >>we'll give you the current database for repair. > >> > >>Thanks for the help everyone with the suggestions, and in verifying the > >>problem! > >> > >>Best Regards, > >> > >>Ed Barnard, maybe a legacy deluxe user again soon > >> > >> > >>On Sun, 2005-09-11 at 15:26, Wm Voss wrote: > >> > >> > >>>I imported your Original into your Clone and ran IntellShare/Merge > >>>and got 89 records that could not be auto merged, just as you did. > >>>I copied the pairs of notes out of a dozen records and did a file > >>>compare in UltraEdit; none showed any difference at all. I also > >>>did compares on the full family files and on exported gedcoms; no > >>>difference found in either. > >>> > >>>Beats me what's going on, but I'd sure not trust it until someone > >>>figures out the problem. > >>> > >>>Wm Voss > >>> > >> > >>Legacy User Group Etiquette guidelines can be found at: > >>http://www.LegacyFamilyTree.com/Etiquette.asp > >> > >>To find past messages, please go to our searchable archives at: > >>http://www.mail-archive.com/legacyusergroup%40mail.millenniacorp.com/ > >> > >>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 find past messages, please go to our searchable archives at: > >>http://www.mail-archive.com/legacyusergroup%40mail.millenniacorp.com/ > >> > >>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 find past messages, please go to our searchable archives at: > >http://www.mail-archive.com/legacyusergroup%40mail.millenniacorp.com/ > > > >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 find past messages, please go to our searchable archives at: > http://www.mail-archive.com/legacyusergroup%40mail.millenniacorp.com/ > > 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 find past messages, please go to our searchable archives at: > http://www.mail-archive.com/legacyusergroup%40mail.millenniacorp.com/ > > 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 find past messages, please go to our searchable archives at: http://www.mail-archive.com/legacyusergroup%40mail.millenniacorp.com/ To unsubscribe please visit: http://www.legacyfamilytree.com/LegacyLists.asp
