Chris, If you spend time to pick it apart logically and apply how all the computations would happen to maintain the database, you would understand better why it is the way it is.
Your scenario is not uncommon, but it cannot be logically programmed. I am not good at explaining things (especially when having to type it out) But maybe if you think of the couple as a distinct point made up of 1/2 from M and 1/2 from F (Or other types) Without the second half present the event should NOT be connected to the remaining half A marriage record MUST always be 2 parts, even if you have only entered 1 name, a marriage needs two parts for the logic to happen. Dont think of marriages as a shared event A shared event is when two people are present at the same place If one person is taken away the other person is still there and the event still applies (just no longer shared) Hope that helps Jay On Fri, Oct 31, 2014 at 1:54 PM, Chris Brady <[email protected]> wrote: > Jay, > > > > I just find it odd, if you will, that even though it is a shared event > under the marriage, electing to show shared events will not result in in > showing on an individual’s report. Just because an event happened during a > marriage – why would an individual’s report act as though the event never > happened at all? > > > > Whereas if it were added to the husband as an event and then shared with > the wife – it would show on the wife’ report if the option to show shared > events was selected. It would always show on the husband’s individual > report. > > > > The behavior is inconsistent. They are both events. In the first case, > both the husband & wife are principals to an event. In the second case, the > husband is the principal. Why would the wife’s individual report in the > first case omit the event entirely? > > > > I don’t understand the distinction that because there are two principals > to an event – that it is somehow not part of an individual’s history. > During the course of a marriage, there are many activities that may be done > as a couple – buying property, establishing residencies, etc. It appears > that I am perceiving the marriage events in Legacy incorrectly and they are > not meant for that. > > > > Thanks for your insight Jay, > > > > Chris > > > > > > *From:* Jay Wilpolt [mailto:[email protected]] > *Sent:* Friday, October 31, 2014 2:25 PM > *To:* [email protected] > *Subject:* Re: [LegacyUG] Shared events on reports > > > > Chris, > > I have been adding events to "marriages" even before 'shared events' came > along in Ver 8. > > These work great for events where the couple is the focus, like a > newspaper marriage or anniversary event. And they will show on reports (as > events for that marriage) not under individual's because the event is added > to only the marriage. > > You could duplicate it for each individual, but then it would most likely > appear thee times on a report. > > Jay > > > > On Fri, Oct 31, 2014 at 9:57 AM, Chris Brady <[email protected]> > wrote: > > Thanks Paula, > > > > Brian had responded earlier with this: > > > > *“1. The Individual Report does not include Marriage Events whether these > are for the person's marriage(s) or are shared from another couple so > electing to include shared events will not include shared marriage events.* > > > > *2. Your assumption that sharing a marriage event means that it becomes a > shared event for the persons in the couple is also incorrect. The husband > and wife in a marriage are the principals for any events in their marriage > not a person who is sharing. That is why the marriage event for the couple > will only be included in an FGR for them and are not listed as shared event > for the husband in FGRs for any other marriages.”* > > > > That seems to indicate that shared marriage events are basically second > class events that do not have the same status as other events. I had > intended to use them for events that both husband & wife shared during the > course of a marriage – ie, if both bought property together etc as that > would help show the course of events during their lifetime. However, it > really doesn’t work when none of those events will show on reports, > especially if they had other spouses during their lifetime. > > > > Thanks, > > Chris > > > > > > *From:* Paula Ryburn [mailto:[email protected]] > *Sent:* Wednesday, October 29, 2014 11:13 AM > *To:* [email protected] > *Subject:* Re: [LegacyUG] Shared events on reports > > > > Chris, I don't use the new shared events, but I'll venture a guess here. > You have added a marriage event for this couple... sure, it's "shared" by > these two, but I doubt anything has been added into the new tables/fields > for shared events. The fact that it shows up only for this couple supports > it not being one of the new shared events. If you didn't go through the > new windows to enter roles, etc., then this is not really a shared event > per the programming logic. Just my guess. --Paula > > > ------------------------------ > > *From:* Chris Brady <[email protected]> > *To:* [email protected] > *Sent:* Thursday, October 23, 2014 2:11 PM > *Subject:* [LegacyUG] Shared events on reports > > > > Has anyone been using shared events created under the marriage tab? > > > > Using Build 439, I created a shared event under the marriage tab of a > couple. By default, that would make it a shared event between those two > people. > > > > The event will only print on a family group sheet for that exact couple > (the husband has multiple marriages). One of the report options – event > options - is “include events they shared from another person or marriage”. > > > > Regardless of whether that is checked or not – if I print a group sheet > for the husband with a wife other than the one with whom I did the shared > event – that event does not show up. The event also does not show up when > an Individual Report is printed on the husband – again, even when the > “include events they shared from another person or marriage” is selected. > > > > I’ve played with every combination under Report Options – Event Options > for both reports – and I cannot get the event to print. As it does print > when that couple is the focus of a Family Group Sheet Report – it does not > seem that it is the option selection which is the cause of the print > problem. > > > > I’d appreciate any advice on what I’m doing wrong. I’d love to be able to > use shared events at this level, but not if I can’t get them to print. > > > > Regards, > > Chris Brady > > > > 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 > > > > 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 > > > 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
