McLemoreStrong
Genealogy
Strong - McLemore History and Ancestry
First Name:  Last Name: 
[Advanced Search]  [Surnames]

Eleanor Rose McLemore

Female 1925 - Yes, date unknown


Personal Information    |    Sources    |    Event Map    |    All    |    PDF

  • Name Eleanor Rose McLemore  [1, 2
    Born 11 Aug 1925  Indiana Find all individuals with events at this location  [1, 2
    Gender Female 
    Died Yes, date unknown 
    Notes 
    • She was listed simply as born August 11, 1920 (?) to Albert McLemore of Kentucky and Dollie Mae Stricking of Daviss County, Indiana. However, the
    Person ID I33972  Strong Family Tree
    Last Modified 17 Aug 2014 

    Father Albert Owen McLemore,   b. 14 Jan 1878, Indiana Find all individuals with events at this location,   d. Yes, date unknown 
    Mother Dorothy "Dollie" Mae Stringer,   b. Abt 1898, Indiana Find all individuals with events at this location,   d. Yes, date unknown 
    Married Abt 1915-1916 
    Family ID F10775  Group Sheet  |  Family Chart

    Family Hugh Thomas Mattingly,   b. 24 Jul 1922, Washington, Daviess County, Indiana Find all individuals with events at this location,   d. 25 Jun 1999, Hartford City, Blackford County, Indiana Find all individuals with events at this location  (Age 76 years) 
    Married 4 Jul 1942  Daviess County, Indiana Find all individuals with events at this location  [1
    • His Indiana Marriage certificate showed that he was born on 24 July 1920 in Washington, Indiana, and was a resident of Adon, Indiana at the time of his marriage, working as an engineer. His parents were shown as Peter Mattingly, also born in Washington, Ind and the late Lillie Clements, born in Jasper, Indiana. He had not been previously married.
    Last Modified 1 Jan 2014 
    Family ID F10776  Group Sheet  |  Family Chart

  • Event Map
    Link to Google MapsBorn - 11 Aug 1925 - Indiana Link to Google Earth
    Link to Google MapsMarried - 4 Jul 1942 - Daviess County, Indiana Link to Google Earth
     = Link to Google Earth 

  • Sources 
    1. [S667] RootsWeb's WorldConnect Project, (The WorldConnect Project is a set of tools, which allow users to upload, modify, link, and display their family trees as a means to share their genealogy with other researchers. The program used to day has a genealogy of its own. RootsWeb announced the launch of the World Connect Project on November 10, 1999 after staff members and users submitted 5.5 million records during a four-week beta-testing period. The WorldConnect Project continues to grow, and as of January 2004 had more than 312 million records. GEDCOM is an acronym for GEnealogical Data COMmunications. It is a file format developed by the Family History Department of The Church of Jesus Christ of Latter-day Saints (LDS). It provides a flexible and uniform format for exchanging computerized genealogical data, and allows you to share files with other researchers who may not use the same genealogy program.), Riser, Jefre (jefre@verizon.net) "Riser Family" Ver. 2007-1 1-13 ; http://wc.rootsweb.ancestry.com/cgi-bin/igm.cgi?db=: 2049892 (Reliability: 3).

    2. [S564] 1930 United States Federal Census [Ancestry.com. database on-line]. Provo, UT, USA: The Generations Network, Inc., 2002., (Original data: United States of America, Bureau of the Census. Fifteenth Census of the United States, 1930. Washington, D.C.: National Archives and Records Administration, 1930. T626, 2,667 rolls. Containing records for approximately 123 million Americans, the 1930 United States Federal Census is the largest census released to date and is the most recent census available for public access. The census gives us a glimpse into the lives of Americans in 1930, and contains information about a household?s family members and occupants including: birthplaces, occupations, immigration, citizenship, and military service. The names of those listed in the census are linked to actual images of the 1930 Census.), Indiana, Daviess County, Washington Twp, Washington City, Third Ward Enumerated 22 Apr 1930 ED 14-19 SD 10 Sheet 27B 714-522-561 (Reliability: 3).