yxe_98 wrote: > I created a basic GEDCOM in Legacy 5.0 deluxe and imported it into FTM 11. > I get the following error:
<snip> > Line 3260 : Tag: REPO, has an invalid CRI: @R32, line ignored. > > Here is the relevant portion of the GEDCOM file: > > 0 @S2@ SOUR > 1 TITL JRI-Poland database > 1 AUTH JRI-Poland > 1 PUBL http://www.jewishgen.org/jri-pl > 1 REPO @R32@ > > When I encountered this problem on the import of the GEDCOM, I moved the > website reference to the publication facts tab. > But the error did not go away. > > What could be wrong? I don't know what FTM's exact problem is that makes it complain about an "invalid CRI". But I do know that the REPO tag is used by GEDCOM to describe a repository. So your snippet of GEDCOM is saying that the jewishgen source is at the repository which is described at label "@R32@". But my version of FTM does not handle repositories with anything approaching Legacy's sophistication. On the master source dialog box there is a field for location. One could put the "repository" of the source in the location field. So what I think is happening is that FTM uses the REPO tag for this location item and when it sees a "label/pointer" with that tag, which is probably valid GEDCOM syntax, it dies because it doesn't know how to deal with such labels on a REPO tag. It doesn't deal with such tags because FTM doesn't maintain a database of repositorys within the overall database of it's family file as Legacy does. So FTM gets lost because it can't handle one of Legacy's features. I occassionally move data from Legacy to FTM via GEDCOM. I've learned to ignore all the errors FTM generates. That's because nearly all the stuff I want to use FTM for gets moved over just fine. Whatever stuff doesn't get translated correctly, I don't care about because I've got it in Legacy. If I were going to move permanently from Legacy to FTM, it would be a issue, but since Legacy is my "main" genie program, it doesn't matter to me. I just use FTM for making family trees, it's good at that -- IMO as good as Legacy's add-ons. But if you are moving permanently to FTM, then you will probably have some problems with getting all your repository information out of Legacy and into FTM. You'll probably have to put it in some notes somewhere since FTM doesn't have data structures to handle all of Legacy's repository info. jr 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
