Hey Ron, The intent behind my original question was that I was going to find a way to find the persons in my database who are twins, BUT that I have not yet marked as twins. And I did not know what table or field I would need to change. I have since discovered that the flag is the IDCS field within the tblCR. In my file changing that from the default of 0 to a 6 will set them as a Twin. The setting for Adopted is a 5 and Quadruplets is 8, not sure yet what it should be for Triplets......
Your scripts will be a great help!! (Just FYI, your first script on same names will be invaluable!! I have mostly Dutch, German and Irish families. The Germans in particular in probably well over 50 % of my families all re-used names and to make it more complicated the names used by the priests on records could easily be different at a baptism, (Johann Friederick Wilhelm) then at marriage (Frederick Wilhelm) then at death (Frederick) I have often wondered why there is not a centralized place where SQL scripts could be found, as they can be such a timesaver. I have a rather large database of just under 250,000 and tasks like marking Twins could take weeks of work without the SQL help. In a response to another part of this thread you mentioned another script you had, could you send that to me as well? I will let you know if I need anymore help. Thanks again for taking th etime to respond WITH all the great code! Jay On Mon, Jul 7, 2014 at 9:11 PM, Ron Taylor <doit4...@yahoo.com> wrote: > Jay, > This first script is one that I developed to locate duplicate siblings in > the database. These are situations where a child is given a name that the > parents want but then dies early so they give the same name to another > child. Sometimes more than twice. It illustrates the connection of the > child status to the child record which is linked to the individual record. > > SELECT tblCR_A.IDMR, tblCR_A.IDIR, tblCR_B.IDIR, tblIR_A.Surname, > tblIR_A.GivenName, tblIR_B.GivenName, tblIR_A.Gender, tblIR_B.Gender, > tblCS_A.ChildStatus, tblCS_B.ChildStatus > FROM (tblCR AS tblCR_A INNER JOIN tblIR AS tblIR_A ON tblCR_A.IDIR = > tblIR_A.IDIR) INNER JOIN tblCS AS tblCS_A ON tblCR_A.IDCS = tblCS_A.IDCS, > (tblCR AS tblCR_B INNER JOIN tblIR AS tblIR_B ON tblCR_B.IDIR = > tblIR_B.IDIR) INNER JOIN tblCS AS tblCS_B ON tblCR_B.IDCS = tblCS_B.IDCS > WHERE (((tblCR_A.IDMR)=[tblCR_B].[IDMR]) AND > ((tblCR_A.IDIR)<[tblCR_B].[IDIR]) AND > ((tblIR_A.GivenName)=[tblIR_B].[GivenName])) > ORDER BY tblCR_A.IDIR; > > This next script will find individuals that are linked to multiple parents > and how the relationship to each parent is linked. > > SELECT tblCR.IDIR, tblIR.Surname, tblIR.GivenName, tblCR.IDMR, > tblMR.HusbSurname, tblMR.HusbGivenName, tblMR.WifeSurname, > tblMR.WifeGivenName, tblIR.IDMRParents, tblCP.CPRelation, > tblCP_1.CPRelation, tblCR.IDCPDad, tblCR.IDCPMom > FROM (((tblCR INNER JOIN tblMR ON tblCR.IDMR = tblMR.IDMR) INNER JOIN > tblIR ON tblCR.IDIR = tblIR.IDIR) INNER JOIN tblCP ON tblCR.IDCPDad = > tblCP.IDCP) INNER JOIN tblCP AS tblCP_1 ON tblCR.IDCPMom = tblCP_1.IDCP > WHERE (((tblCR.IDCPDad)>1)) OR (((tblCR.IDCPMom)>1)) > ORDER BY tblCR.IDIR, tblCR.IDMR; > > Finally, this script will find all individuals with child status Twin and > illustrates how the status is linked to the individual. > > SELECT tblCR.IDIR, tblIR.Surname, tblIR.GivenName, tblCS.ChildStatus > FROM (tblCR INNER JOIN tblCS ON tblCR.IDCS = tblCS.IDCS) INNER JOIN tblIR > ON tblCR.IDIR = tblIR.IDIR > WHERE (((tblCS.ChildStatus) Like "Twin")); > > Hope that helps you with your quest. > Ron Taylor > > > > On Monday, July 7, 2014 7:59 PM, Jay 1FamilyTree < > 1familytree....@gmail.com> wrote: > > > > > When I change a child status from the default of '_' to 'TWIN', > > What field changes in the database? > > I cannot see any changes in the IR table for Individuals > Or is there somewhere else I should be looking? > > Thanks 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/legacyusergroup@legacyusers.com/ > Archived messages from old mail server - before Nov. 21 2009: > http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/ > 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/legacyusergroup@legacyusers.com/ > Archived messages from old mail server - before Nov. 21 2009: > http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/ > 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/legacyusergroup@legacyusers.com/ Archived messages from old mail server - before Nov. 21 2009: http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/ 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
