From: Alain A. <ala...@wa...> - 2009-09-01 07:27:14
|
Michael Lightfoot a écrit : > To be divorced one has to be married. The relationship type is therefore > "married", but there are events for marriage and divorce. This is how I have done it. > I agree, but it's a little confusing when editing reports, and to be divorced, we must first have been married, so the 'married' state isn't hidden by 'divorced', the opposite isn't right. > It may seem a little confusing at first, but the type is the family type and if a marriage took place the type should be "married". Here are some > examples. I have one woman in my tree where there was one family involving marriage which ended in the husband's death and then one which had no marriage. I personally have two families, both of which involved marriage events and the first of which involved divorce events. > I think death has not the same effect as divorce, When someone is dead, the marriage is always existing, what isn't the reality when a divorce is pronounced. A+ |
From: Benny M. <ben...@gm...> - 2009-09-01 07:54:09
|
2009/9/1 Alain AUPEIX <ala...@wa...>: > Michael Lightfoot a écrit : >> To be divorced one has to be married. The relationship type is therefore >> "married", but there are events for marriage and divorce. This is how I have done it. >> > I agree, but it's a little confusing when editing reports, and to be > divorced, we must first have been married, so the 'married' state isn't > hidden by 'divorced', the opposite isn't right. The way it is is that you have a family, which is married, or cohabitating, or ...., and you add a marriage event. When the family divorces, you add a divorce event, and create a new family for the father and mother if there are children, adding the children there as per the newly formed families after the divorce. So the divorce is the end of the family object. A death of a parent is not. One should not change the relationship string. If a report prints marriage although there is a divorce event, then the report must be changed. Benny >> It may seem a little confusing at first, but the type is the family type and if a marriage took place the type should be "married". Here are some >> examples. I have one woman in my tree where there was one family involving marriage which ended in the husband's death and then one which had no marriage. I personally have two families, both of which involved marriage events and the first of which involved divorce events. >> > I think death has not the same effect as divorce, When someone is dead, > the marriage is always existing, what isn't the reality when a divorce > is pronounced. > > A+ > > > > > ------------------------------------------------------------------------------ > Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day > trial. Simplify your report design, integration and deployment - and focus on > what you do best, core application coding. Discover what's new with > Crystal Reports now. http://p.sf.net/sfu/bobj-july > _______________________________________________ > Gramps-users mailing list > Gra...@li... > https://lists.sourceforge.net/lists/listinfo/gramps-users > |
From: Duncan L. <dun...@gm...> - 2009-09-01 13:14:35
|
2009/9/1 Benny Malengier <ben...@gm...>: > One should not change the relationship string. If a report prints > marriage although there is a divorce event, then the report must be > changed. +1 Please make a bug report about the reports which you think misrepresent the facts. Duncan |