Have you tried viewing the GEDCOM file in Notepad (or similar) at entries
around #14035? There might be a stray character or missing ENTER or some
other oddity that you can spot visually and fix. This could be right at
14035, or it might be a few before or after that entry.
Obviously do this "fixing" to a backup of the GEDCOM file!
Is it possible to re-create the GEDCOM file from the original source? Maybe
during the first creation the program hiccupped and dropped something weird
in there. Or maybe the original program has some other options that can be
tried during the GEDCOM creation.
Bob
----- Original Message -----
From: "Susan Daily" <[EMAIL PROTECTED]>
To: <LegacyUserGroup@legacyfamilytree.com>
Sent: Saturday, October 06, 2007 4:50 PM
Subject: Re: [LegacyUG] Error #6
Did you receive the file from someone else or create it yourself? Can
you import it into another program like FTM or the free LDS software,
PAF? If you can import it into PAF, how about then splitting up one of
the major couples so that you can peel off about 10k-20k names? Then
try exporting to a new GEDCOM and importing then.
Alternatively, has Support contacted you about trying to import the
file themselves, if you are willing to email it to them?
I know there are other LUGgers here who have more than 50k names in
their databases. Perhaps they can do a GEDCOM export, and then try
importing that into a new family file to see if they get the same
error that you do. I only have less than 7k names, so can't help in
that regard.
Susan
On 10/6/07, Melody <[EMAIL PROTECTED]> wrote:
I did try that. The problem with brute-force chopping up the file is
that
info in the last half of the file references stuff in the first half and
those links get broken. But yep, it will except for that import the
files
just fine.
-----Original Message-----
From: Susan Daily
Sent: Saturday, October 06, 2007 3:57 PM
Melody,
can you manually open the GEDCOM file using a text editor like WordPad,
and
simply erase half the file at a time? Then try importing it into a new
test
Legacy file? Then do it again with the other half, opening into a second
test file. Then merge the two files, or simply import from one to the
other?
You might get a lot of broken links at that halfway point, I suppose.
Guess this isn't such a great idea after all!
Susan
On 10/5/07, Melody B <[EMAIL PROTECTED]> wrote:
> I searched the archives first. At that time, it seems that Legacy
> indicated that this was due to a bug which would be fixed in the next
> build. Since I got Legacy a couple of months ago, I assume I got the
> most
recent bug.
>
> Does anyone know if this bug was fixed?
>
> My bug... I try to import a GEDCOM of 46K+ people into a new family
> tree and Legacy croaks on person #14035. I tried the work-arounds
> that seem to sometimes help (moving dot usr files) but it didn't. I
> suspect that Legacy can actually handle the file no problem if I could
> only get it imported. If I had a method of splitting the gedcom into
> smaller pieces, I suspect I could work around this. But the only
> thing I've seen that will split GEDCOMs is GenSplit (or something
> like) which doesn't actually seem to exist any more.
Legacy User Group guidelines:
http://www.LegacyFamilyTree.com/Etiquette.asp
Archived messages:
http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/
Online technical support: http://www.LegacyFamilyTree.com/Help.asp
To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp
Legacy User Group guidelines:
http://www.LegacyFamilyTree.com/Etiquette.asp
Archived messages:
http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/
Online technical support: http://www.LegacyFamilyTree.com/Help.asp
To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp
