This is not directly in response to Steve’s question, but more a comment on how the shared events function in general.
Earlier there was some discussion about the shared event being a proprietary format, and what programs might or might not take advantage of Legacy’s codes. I didn’t pay a lot of attention to that discussion since it mentioned programs I do not use myself. However, for those of us who export gedcoms from Legacy to post a tree someplace else (such as on Rootsweb or Ancestry or published via another competing software program), the shared event will export solely under the name of the person whose event is being shared. I tested with a census — under the head of house’s census event it all displayed normally, but then following that event I got all the shared events for every other household member — but it shows up on the head’s page and not in the data of the other household members. This, for me, makes shared events useless since the census data won’t appear on the household member’s page in my Rootsweb exports. This makes sense when you think about it, because of the limits of the gedcom format. Still, I wanted to warn people up front in case they got excited doing a lot of shared events and only later found out how it might adversely affect their publishing. 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
