Ed, to check this further, I created 2 matching files, one from my v.5
database and the other from my v.6 database; each have the same 114
individuals and I was careful to do the export/import stuff exactly the
same way each time.
I then created a new database, and imported both the v5 and v6 versions,
then used automerge. All but 19 automerged, and those 19 all had "Abt"
or "Est" birthdates. Those could easily have been automerged by
changing my merge-specs, or would not have taken very long to merge
manually had I so chosen.
So again, that seems to verify that you have a corrupted database. If
you can't get it straightened out with check/repair, you'll need to have
Sherry give you their procedure for attaching/sending your database for
a fix. that's [EMAIL PROTECTED]
This really doesn't tell us much about "Intellishare fails".
now off-subject, but I did notice that v.6 Standard accepts only tags
1-3. That was a bit upsetting because my 114 people were v.5 - tagged
9. However, Search still contains the field Tag 9, so was able to work
around that.
You'll be okay, just may take a couple of days. It's no reason to give
up on Legacy - my gosh, nothing else comes close!
RonKZ
Ron Klotz Zellhoefer
now in Deming, NM USA
researching Zellhofer/Fellhofer/Wellhofer/variations
http://zelltree.com
Ed Barnard wrote:
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
