That's Easy?????? Aside from that - not everyone uses (or wants to use) LTools - and I'd rather not clear my UserID's just to set reminders or tag more than one marriage at a time.
On 11 January 2014 13:00, Ron Taylor <[email protected]> wrote: > I actually use the marriage tags quite a bit. Here is a help file that I > sent out recently to some of the local Legacy users. It sets the marriage > record "Anniversary Reminder" but logic to set any of the marriage tags is > similar. The process makes it easy to set all the Birthday Reminders and > Anniversary Reminders for descendants of select ancestors...ie living > cousins, etc. > > How to set Anniversary and Birthday Reminders for select individuals > 1) Clear tag5 and all UserIDs for everyone in the Legacy database. > You may also want to clear all Anniversary and Birthday Reminders so those > set by this procedure are not mixed with others. > 2) Make list of RINs for grandfathers or great-grandfathers or any > other group. > 3) Set tag5 for all descendants (including spouses) of RINs from step > 2. Easily done with a Focus Group. First “Clear List” to start with an > empty Focus Group. Then click “Add an Individual and Descendants” for each > RIN. Then Search>Miscellaneous>Focus Group>Create List>Options>Advanced > Tagging>Tag on #5>Everyone in Search List. Exit from Legacy. > 4) Set UserID for all biological descendants of the RINs from step2 > with Ltools>Set Special User IDs. Set radio button “Fill descendant’s User > ID with Text + Henry Number”. Enter “HN-“ in the Text field. Check the > box “Exclude Non-Biological Relationships”. Click “Run” and “Continue”. > The number of rows (User IDs for individuals) affected will be displayed. > Exit from Ltools. > 5) This SQL script will set the Anniversary Reminder for all marriage > records where the marriage status is blank, “This couple did not marry” is > unchecked, both spouses are living and have tag5. > UPDATE (tblMR INNER JOIN tblIR ON tblMR.IDIRHusb=tblIR.IDIR) INNER JOIN > tblIR AS tblIR_1 ON tblMR.IDIRWife=tblIR_1.IDIR SET tblMR.ReminderTag = 1 > WHERE (((tblMR.IDMS)=1) And ((tblMR.NotMarried)=0) And ((tblMR.IDIRHusb)>0) > And ((tblMR.IDIRWife)>0) And ((tblIR.Tag5)=1) And ((tblIR_1.Tag5)=1) And > ((tblIR.Living)=0) And ((tblIR_1.Living)=0)); > 6) This SQL script will set the Birthday Reminder for husbands of the > marriages affected in step 5. > UPDATE tblMR INNER JOIN tblIR ON tblMR.IDIRHusb=tblIR.IDIR SET > tblIR.ReminderTag = 1 WHERE (((tblMR.ReminderTag)=1)); > 7) This SQL script will set the Birthday Reminder for wives of the > marriages affected in step 5. > UPDATE tblMR INNER JOIN tblIR ON tblMR.IDIRWife=tblIR.IDIR SET > tblIR.ReminderTag = 1 WHERE (((tblMR.ReminderTag)=1)); > 8) This SQL script will set the Birthday Reminder for all living > biological descendants from step 4. Some of these may already have been > set in step 6 or step 7 if they were linked to an active marriage. > UPDATE tblIR SET tblIR.ReminderTag = 1 WHERE (((tblIR.UserRef) Like > "HN-*") AND ((tblIR.Living)=0)); > 9) Each of the SQL scripts could be executed by Ltools>“Run Raw SQL”. > Also, Ltools>”Set Birthday/Anniversary/Death Reminders” could be used to > turn off or turn on the reminders. You will first have to set a tag for > the individuals or marriages that this process will affect. The birthday > reminders can be tagged with Search>Detailed Search>Individual>Birthday > Reminder>Equal to>Checked>Create List>Options>Advanced Tagging>Tag on > #1>Everyone in Search List. The anniversary reminders can be found with > similar logic but Legacy does not provide a method for setting the marriage > tags. This SQL script will set marriage tag5 if the Anniversary Reminder > is set and then use it in Ltools. > UPDATE tblMR SET tblMR.Tag5 = 1 WHERE (((tblMR.ReminderTag)=1)); > 10) This final search may find a few non-biological living descendants or > connected spouses for whom you may want to set the Birthday Reminder. They > might be step children of a biological descendant, spouse of a deceased > descendant, a divorced spouse, an unmarried spouse, or other linked > individuals. Search>Detailed Search>Individual>Tag5>Equal to>Tagged and > Individual>Birthday Reminder>Equal to>Unchecked and Individual>Living>Equal > to>Yes. > 11) A marriage marked “This couple did not marry” should be considered as > having status “Unmarried” even if that status has not been explicitly > entered. They will be excluded like the divorced spouses if status is > non-blank. This SQL script can detect those who “did not marry” with blank > marriage status. > SELECT tblMR.IDMR, tblMR.IDIRHusb, tblMR.HusbSurname, tblMR.HusbGivenName, > tblMR.IDIRWife, tblMR.WifeSurname, tblMR.WifeGivenName, tblMR.IDMS, > tblMR.NotMarried FROM tblMR WHERE (((tblMR.IDMS)=1) AND > ((tblMR.NotMarried)=1)); > > > On Thursday, January 9, 2014 9:47 PM, CE WOOD <[email protected]> wrote: > Yes, it is. > > > CE > > ------------------------------ > From: [email protected] > To: [email protected] > Subject: RE: [LegacyUG] Tagging marriages > Date: Thu, 9 Jan 2014 16:19:33 -0800 > > “in my 100+ generations” > That is a bit to many, I think you need to do another count? > That is back to the BC time period? > > Thanks, > David C Abernathy > Email disclaimers > > ---------------------------------------------------------------------------- > This message represents the official view of the voices in my head. > > ---------------------------------------------------------------------------- > http://www.SchmeckAbernathy.com <http://www.schmeckabernathy.com/> > == All outgoing and incoming mail is scanned by F-Prot Antivirus == > > *From:* CE WOOD [mailto:[email protected]] > *Sent:* Thursday, January 09, 2014 4:09 PM > *To:* [email protected] > *Subject:* RE: [LegacyUG] Tagging marriages > > To get a complete picture, you also need to do the paragraph 3 search for > females. There are more marriages where the ancestry of the wife is > unknown, but there are several in my 100+ generations where the ancestry of > the husband is unknown. To be thorough, do both. > > Considering the number of generations I and others have, I do hope Legacy > will soon include the ability to tag Marriage Tags to accommodate tracing. > > > CE > > > From: [email protected] > > To: [email protected] > > Subject: RE: [LegacyUG] Tagging marriages > > Date: Thu, 9 Jan 2014 16:22:49 -0600 > > > > Marriage Tags and Individual Tags are separate. Unfortunately, there is > not yet an advanced tagging function for the Marriage Tags. They can only > be turned on/off one at a time. > > > > Best I can think of is to use advanced tagging to tag your direct > ancestors (exclude siblings, etc, and limit to the desired number of > generations. > > > > You can then create a search list based on that tag and perhaps limit > the search list to just the males. Then you could go through that search > list to set the marriage tags. > > > > > > -----Original Message----- > > From: Bernd Hornung [mailto:[email protected] <[email protected]>] > > Sent: Thursday, January 09, 2014 3:43 PM > > To: [email protected] > > Subject: [LegacyUG] Tagging marriages > > > > I would like to tag all direct ancestor marriages to tagged 8th and 9th > generation grandparents. I have them tagged #1 and have a search list. > > > > Is there a way to use this to tag the intervening marriages as marriage > tag #1. This presumes that the tags are different between general and > marriage tags. If not I can use a different tag #. > > > > I would like to use the tags as a research guide and not have to work > down the marriage list (8400) one by one, not knowing right off, which are > direct ancestors and which are 5th cousins 5x removed. > > > > Any pointers to directions or assistance is 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 > > > > > 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
