bgsu1976, The real problem is that Legacy or any software company does not own the standards of GEDCOM. These standards were late updated in the early 90's and will not be updated. Most of the software companies do comply with the requirements of GEDCOM.
I know that these standards do NOT include media and attachments; I am not sure if they are including the sources completely. Again what were the source standards back in the 90's and I am sure that is what is included in the GEDCOMs made today. Yes, there are several groups out there that are trying to come up with a "New" GEDCOM, but then ALL of the software companies will have to buy in on it. Thanks, David C Abernathy Email disclaimers ---------------------------------------------------------------------------- This message represents the official view of the voices in my head. ---------------------------------------------------------------------------- http://www.SchmeckAbernathy.com == All outgoing and incoming mail is scanned by F-Prot Antivirus == -----Original Message----- From: [email protected] [mailto:[email protected]] Sent: Friday, October 05, 2012 8:41 AM To: [email protected] Subject: Re: [LegacyUG] Another problem -- sorry! -- with source list names in a new .gedcom Mike Fry <[email protected]> proclaimed: >Why? I'd never use a GEDCOM to go from Legacy to Legacy. It's far >better and more comprehensive to use the native file format. I agree, but sometimes there is no other way to fix a database problem. A native export just uses SQL to copy a table from one database to another. Some problems are likely to get copied with it. I vaguely recall seeing LUG posts where GEDCOM export/import was recommended by Millennia as the suggested alternative to fixing a problem after all else had failed. Although I have to admit that I haven't seen this recommendation recently. But it doesn't change my opinion (and I believe others would agree), that the Legacy format GEDCOM export/import cycle should produce a 'virtually' identical database. Obviously there would be some differences, such as a list of deleted RINs/MRINs would probably be absent. -- bgsu Legacy User Group guidelines: http://www.LegacyFamilyTree.com/Etiquette.asp Archived messages after Nov. 21 2009: http://www.mail-archive.com/[email protected]/ Archived messages from old mail server - before Nov. 21 2009: http://www.mail-archive.com/[email protected]/ Online technical support: http://www.LegacyFamilyTree.com/Help.asp Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) and on our blog (http://news.LegacyFamilyTree.com). To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp Legacy User Group guidelines: http://www.LegacyFamilyTree.com/Etiquette.asp Archived messages after Nov. 21 2009: http://www.mail-archive.com/[email protected]/ Archived messages from old mail server - before Nov. 21 2009: http://www.mail-archive.com/[email protected]/ Online technical support: http://www.LegacyFamilyTree.com/Help.asp Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) and on our blog (http://news.LegacyFamilyTree.com). To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp
