I do not agree on that Gedcom is that bad. If you read the standard you find that it supports a lot of good stuff. It is the software that use Gedcom that does not implement Gedcom 5.5 correct. Each software implements its own little corner of Gedcom 5.5 so the common part is not that powerful.
The problem is that the packagers that use Gedcom does not have an internal data structure for all Gedcom's structures. This will not go away with an XML standard.
sow/
At 10:07 AM 4/6/04, you wrote:
Also promoted with either suite is some integration with a database app called "Adabas D" - which via ODBC / SQL would be capable of R/W of the underlying Legacy/MSaccess data. (I've not seen Adabus - have used Lotus Approach for ditto). Adabas is not cheap, but I'm not sure at what point one might need to own it.
Perhaps a more / better aspect of these suites is integration with XML, which is destined to replace HTML. XML holds much promise in the area of universal document standards, and can be expected to replace e.g. GEDCOM, which would be a blessing to us all. For those who are moving data back/forth between Legacy and other gen-apps - be ASSURED your data will get screwed up via GEDCOM! Gedcom is so bad that I will no longer exchange data except as a Legacy file (usually a backup.zip)
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
