OK, one last try before I begin manually adding over 3,000 new Facts. Has RM created a way to import Find A Grave ID#'s from Legacy Family Tree (which I’m leaving) into my RM database? I asked awhile back and the answer was no. Just thought I would try one last time. So much of Legacy’s data is captured in a GEDCOM import, why not the Find A Grave?
I’m not familiar with the previous discussion. Have You already examined the databasename.LST file that is created whenever RM imports a Legacy Family Tree GEDCOM for any error logging that reports being unable to recognize Find A Grave ID#'s? That’s its purpose… to show tag structure rejection.
Also, exactly what do the Find A Grave ID#'s look like in the GEDCOM produced by Legacy Family Tree? The answer may be in the previous discussion, but I can’t remember the previous discussion.
If RM can’t import them as they are, there might be a way to edit the GEDCOM with a text editor to convert the Find A Grave ID#'s into a format that RM can import.
I can answer the question about what the FaG export looks like in GEDCOM. I still have a test file that I did some time ago for my father. He is the only person in the GED file and the FaG export shows:
1 _FGRAVE 175768540
1 _FGLINK Kenneth Marion Funk Sr. (1946-2003) - Find a Grave Memorial
The .lst file shows the following from importing it into RM7:
Unknown info (line 78)
1 _FGRAVE 175768540
Unknown info (line 79)
1 _FGLINK Kenneth Marion Funk Sr. (1946-2003) - Find a Grave Memorial
I just noticed that pasting the findagrave URL into the message window actually converted it to the page name .
If the OP doesn’t get to it, I can create another GED file with older relatives so that I can post a bigger chunk of the GED file if it is needed. The GED was exported from Legacy 10.
1 Like
Very Cool. Then, as thejerrybryan mentions, the OP ~may~ be able to filter for folks with FaG facts and export a GEDCOM for possible Search and Replace tag restructuring from within a text editor to achieve Custom Fact parity.
…which was my plan when I started this but it turns out I was too lazy to be bothered since I currently only have Legacy because it is free. I don’t use it normally.
Is there a reason why you do not or cannot use the 32-bit RM 10 for Windows to directly import from your LFT file? It is the only version of RM that can and, according to this FB post answered by @rzamor1 , it imports LFT’s Find A Grave fact: Redirecting...
3 Likes
You can have the 32 bit RM and the 64 bit RM installed on the same Windows computer at the same time. For the most part, their functioning is identical. And indeed, when RM8 was first released, it was released only in a 32 bit version. In other words, it worked fine on an otherwise 64 bit computer (and still does). The 64 bit RM was released sometime later.
The only difference that I’m aware of is that the 32 bit version of RM supports direct import from Legacy Family Tree and the 64 bit version of RM does not. The reason is that Legacy Family Tree is a 32 bit program, and the libraries needed to read a Legacy Family Tree database are 32 bit libraries.
The Mac version of RM only operates in 64 bit and the Mac version of RM therefore does not support direct import from Legacy Family Tree. So if you are a Mac user of RM and if you need to do a direct import from Legacy Family Tree, you would need to find a Windows computer to use just for the import. I don’t know if it’s possible to run the 32 bit RM for Windows using Windows emulation on a Mac.
The reason that RM only runs in 64 bit on a Mac is that macOS itself is no longer compatible with 32 bit programs. The change to being a Mac being incompatible with 32 programs began with macOS Catalina. For the time being, a 64 bit Windows computer is still compatible with 32 bit programs. Such compatibility will surely phase out eventually, but Microsoft is usually pretty slow to phase out backwards compatibility.
The 32-bit version of RM will directly Import the FAG numbers.
Thanks everyone for your replies. Unfortunately all of them were way over my head.
Do you have a Windows computer?
Let’s start over …
You Cannot import individual FAG #s from Legacy into an Existing RM database.
You CAN Import your Legacy with FAG #'s into a NEW RM database.
In RM Go to File>Create New file>Import from RM, gedcom, etc THEN if you see the option to select Legacy you have the 32-bit version.
2 Likes
MadDog,
You’re the best! It worked. A huge thank you. Having Find A Grave ID#s was the only thing holding me back from migrating from Legacy to RM. I’m now a dedicated RM fan.
2 Likes
Glad it worked out for you.