Ron, Sorry for not responding sooner, but this email ended up in my spam folder, glad I found it.
The query worked great and found just what I was looking for, those elusive spouses who somehow have remained LIVING, when they certainly are no longer with us. So thanks for some great code!! Now, what about the spouses who dont actually have a spouse with an RIN but they have a MRIN? As you know, every parenting situation in Legacy is connected to a MRIN, even if no persons are connected to that MRIN.... So, I have in most cases created a Unknown, Unknown spouse when needed, and sure I missed a few, Guess I answered my own question here, probably best to go catch the empty spouses and create the 'placeholders' ....then rerun your query.... And Glad that I found FEWER than you did, but still have almost 600 to review. Again, thanks for the great code. Jay On Tue, Jun 3, 2014 at 5:50 PM, Ron Taylor <[email protected]> wrote: > This query (run in MS Access or Ltools) will find the spouses you want. > If you want both spouses living, change OR in the last line to AND. > If you want birthdate before some other date, change 19200000 to what you > want. > The query could be changed to an UPDATE and perhaps SET one of the > marriage tags for use in Legacy. > > SELECT tblMR.IDMR, > tblMR.IDIRHusb, tblIR.Surname, tblIR.GivenName, tblIR.BirthSD, > tblIR.Living, > tblMR.IDIRWife, tblIR_1.Surname, tblIR_1.GivenName, tblIR_1.BirthSD, > tblIR_1.Living > FROM (tblMR INNER JOIN tblIR ON tblMR.IDIRHusb = tblIR.IDIR) INNER JOIN > tblIR AS tblIR_1 ON tblMR.IDIRWife = tblIR_1.IDIR > WHERE tblMR.IDIRHusb>0 AND tblMR.IDIRWife>0 > AND tblIR.BirthSD>0 And tblIR.BirthSD<19200000 > AND tblIR_1.BirthSD>0 And tblIR_1.BirthSD<19200000 > AND (tblIR.Living=0 OR tblIR_1.Living=0); > > > > On Tuesday, June 3, 2014 4:17 PM, Jay 1FamilyTree < > [email protected]> wrote: > > > Hoping someone might be able to figure out how I can search for 'living' > persons whose Spouse is born before 1920. > > I dont see any way to use dates against spouses in a selection parameter. > > Thanks in advance for any help > > Jay > > > 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
