Thanks Jim. All I wanted to know. I’ll keep this list for future reference.
Sent from Windows Mail
From: Jim Terry/Support
Sent: Friday, December 19, 2014 5:23 PM
To: legacyusergroup@LegacyUsers.com
John,
There are several ancillary files that may show in the data
What are the FamilyName.FG, FamilyName~PPL.PPL, FamilyName~Rc3.Rc3.Cal files?
Are they required if sharing a database with someone else?
Thanks anyone.
John Townsend
Sent from Windows Mail
Legacy User Group guidelines:
http://www.LegacyFamilyTree.com/Etiquette.asp
Archived messages
Thanks Brian and Michele. With your clue that perhaps the original Gedcom file
is the source, I think I have solved the origin of the Attributes event field.
This probably is not of much general interest, but for anybody else who will be
trying to import an old Roots3 database into Legacy,
Thanks Michele. I was hoping for an easier solution than individual edits, but
this will do. Do you have any thoughts on the origin of this “Attributes”
event? I have 3 other large Gedcom (from Roots3) family files to import into
Legacy, and if I could avoid this same phenomenon I would be
I'm a new user of Legacy (v 8.0.0.454) and have a small problem. I imported
a Gedcom file created years ago from a Roots3 (or Roots4?) database that I
helped my mom create. I was pleasantly surprised at how well this import
worked. The relationships are fine; all I have to do is clean up some
5 matches
Mail list logo