Thanks for the warning about GEDCOMs not importing correctly even if they look like they have.
With Error #6, I am given 3 choices: Retry Yes, Retry No, Quit. Retry Yes and No seem to not make any difference at all (I got tired of clicking No after 100 clicks). Clicking Quit closes Legacy completely without warning (whereas I would have expected Quit to quit the import process). So that's what I mean by croaking. On 10/7/07, Stuart Gregory <[EMAIL PROTECTED]> wrote: > > I don't know what you mean by 'croaks' but I believe that Legacy has > at least two problems with importing Gedcoms. I reported the first > problem back in May and I was sent an email from Brian at Support to > say the bug had been listed to be fixed. As at today it hasn't. This > problem related to the fact that Legacy will not import linked media > in accordance with the Gedcom V5.5.1 'standard'. > > I also reported a problem with the import of a largish (5.2 Megs) > Gedcom file back on 3 August. Brian asked for a copy of the Gedcom > which I sent to him. Despite several reminders I have heard nothing > about this. I find this very unsatisfactory and I caution everyone not > to rely on Legacy importing Gedcom files correctly. > > Although my Gedcom didn't make Legacy 'croak' it made a mess of some > families. That is, it linked several people to the wrong mother and > father. Yet when I load the same Gedcom into Genviewer, the data is > correctly displayed. > > I repeat my caution - Legacy is not importing Gedcoms correctly and > you should not rely on the data imported unless you check it very > thoroughly. > > -- > Stuart > Perth Western Australia > 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
