Jim, First of all, please send messages to the LUG list in plain text only.
The problem you had with the import is due to the fact that FTM uses a PLAC tag when it exports Facts. This has been a known issue for *many* releases of FTM. Why they've never corrected it is beyond me! The PLAC tag is reserved for locations and any importing genealogy program will recognize that data associated with that tag as a location and not as a Fact Legacy has provided for this problem with the FTM gedcom by allowing the user who is importing the gedcom to direct where each bit of data with the PLAC tag goes. Also, once the gedcom has been imported into Legacy, if the process was not used to direct the data but that all the Facts went to the Master Locations, then in the Master Location list, click on Options > Options for Non-Locations to send that info to Events. Thanks for using Legacy. Sherry Customer Support Millennia Corporation supp...@legacyfamilytree.com http://www.LegacyFamilyTree.com We are changing the world of genealogy! --------Original Message------------- From: James E [mailto:jamescob...@sympatico.ca] Sent: Sunday, June 13, 2010 11:53 AM To: LegacyUserGroup@LegacyUsers.com Subject: [LegacyUG] A Way to Perform Mass Updates When I migrated my database from FTM to Legacy I ended up with a number of issues with the converted database. These were mostly because of limitations of the release of FTM that I was using, or the consequence of lack of consistency in my early use of the tool. In particular that release of FTM did not separate the description from the location in events. So I had a bunch of "locations" in the location master table like "Farmer, Township, County, Prov/State, Country". When I say a "bunch", I mean like over 5000 of them! So I obtained a description of the internal data structure of the Legacy database from Millenia Corporation technical support. Legacy uses an everyday MS Access JET file, and wrote the following quick Java app to use SQL to make the mass changes. This code is, of course, completely un-warrantied, and is provided only as a framework which you could use to make similar mass changes to your database. Legacy User Group guidelines: http://www.LegacyFamilyTree.com/Etiquette.asp Archived messages after Nov. 21 2009: http://www.mail-archive.com/legacyusergroup@legacyusers.com/ Archived messages from old mail server - before Nov. 21 2009: http://www.mail-archive.com/legacyusergr...@legacyfamilytree.com/ Online technical support: http://www.LegacyFamilyTree.com/Help.asp To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp
