Defacto Marriage - some things to consider

Establishing parent/child joins does not require that the parents need to be "married". Some programs require the parents to be "married" before they allow children. GENP does not require the parents to be married.

So the program works perfectly well with the parent/child joins established. This may be all you require of the program. All the reports and charts will show the issue of the union.

If you want to indicate the defacto marriage between the parents then you need to firstly marry the two parents using a Marriage Attribute.

This is how this can be done:

add a Marriage attribute for the two parents.

 

If you want to indicate that the marriage is a defacto marriage you then add some text to the Memo field of the marriage.

For example key:

(Defacto relationship.)

 

Alternatively key:

(Defacto.)

 

In Narrative reports this will appear like:

John Doe married Jane Doe. (Defacto relationship.)

 

If you want to keep the Defacto relationship private then you would wrap the text in the Memo in private markers:

[[(Defacto relationship.)]]

 

When you create a report you can, on the Miscellaneous tabsheet, uncheck 'Show private data'. In this case the phrase will not appear. You will see:

John Doe married Jane Doe.

 

See the Help under the Privacy topic for more information.

You could also create your own Attribute with your own sentence.

Another method of indicating a Defacto Marriage is to use the Event Attribute.

To generate a sentence like:

John Doe and Jane Doe were in a defacto relationship on 28 Jun 2010.

 

you would key into the Memo field of the Event:

in a defacto relationship

 

and key into the Date field of the Event:

28 Jun 2010

 

The program is very flexible regardless of the method you choose.

(2010 Jul 16)

Share |