Rob Weiss posted:
<snip>
> While I like John's suggestion, and it would work well within Legacy, it
> seems it would have to export via Gedcom as a concatenated text string for
> compatibility with other programs i.e. the same as what happens now. I
> doubt that Gedcom could handle the field descriptors. Still, maybe this is
> not a showstopper, though.
I'm glad you like my suggestion. I like it too! ;-)
Anyway, what you write above is true. I tried to say that in reply
to another posting which I sent a few minutes ago, but I think your
answer is more succinct and clearer. The GEDCOM issue is real.
This would be a feature of Legacy that would pretty much have to
stay within the Legacy database, at least until the GEDCOM
standard (XML Based?) got changed.
jr
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
