Thank you Cathy. Just your mentioning that there was some sort of option for MRINs made me look at the customize option. I played with it a bit and got a report that closely resembles what I wanted. There are a few multiple MRINs to edit and then re-sort. There were 155 lines and I even got it to include the relationship (i.e. 10th Great Grandfather).
Bernie On 15/05/2014 5:42 PM, Cathy Pinner wrote: > Hi Bernd, > > Marriage Tags are not very useful and they can't be applied to a group. You > have to do them one by one. > > Re MRINs on printing a Search List. > > The "include RINs and MRINs" on the first tab only applies to the surrounding > relatives and they're only included in lines between the individuals being > reported. They aren't included when you choose csv output. > You have to choose the RIN and the Spouse's MRIN as fields on one of the Rows > to get it in the report. The Spouse's MRIN returns the MRIN for all spouses > whereas for the name of the spouse you have to specify which spouse. If > you're only interested in particular marriages, then preferred is the way to > go. Otherwise you might want more than one field for spouse names. > > Cathy > > Bernd Hornung wrote: >> Is there a way to tag all direct line marriages as a group? I have set >> marriage Tag 1 as direct line, and general Tag 1 as direct line >> ancestor. Other than doing each marriage manually I would like to >> apply marriag > e tag 1 to all direct line marriages in order to make a >> report that I could manipulate in spreadsheet to mark what events I have >> documentation for and what needs to be found. >> Supplemental - I have a search list of all direct ancestors and under >> print/options I have checked "include RINs and MRINs" but the MRIN does >> not show on the report. I thought if this did I could save as CSV and >> then sort by MRIN to put husband and wives together. The ultimate >> report I would want would be a spreadsheet that shows: >> Name/relationship/birth/death/marriage >> >> I manually made such a chart in much smaller databases but in the >> current DB of 35,000 with many more ancestral lines, it is daunting task. >> >> Any tips or suggestions would be appreciated. >> >> Thanks >> >> Bernie >> >> >> > > > 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 > > -- Bernie H Blog site http://haushornung.weebly.com/ Data site http://www3.telus.net/hornunghouse/ 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
