Gavin, that is exactly what I’m saying. Using a gedcom export, the data shows up ONLY under the event initiator’s dataset.
Keep in mind, however, that if you use Legacy to create your reports, charts, sharing via PDF files, etc. then the shared events should appear properly within the particular reports (according the report options you’ve chosen). The issue is with gedcom export.* cheers, Kirsty J *Or, technically, the issue arises anytime you’re using another software program to handle a Legacy file, be it gedcom or native FDB format. From: Gavin Nicholson [mailto:[email protected]] Sent: Wednesday, December 4, 2013 4:42 PM To: [email protected] Subject: RE: [LegacyUG] Shared vital Events >> 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. Sorry I haven't looked at this yet but are you saying you shared an EVENT with two or more people and when you exported it the shared event only appeared against one person? If so, it doesn't make sense to me I assumed the event would just get copied to the other people when an export occurred? I agree if it doesn't work like this that is a major oversight. Gavin... 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
