Sources |
- [S615] Ancestry.com and The Church of Jesus Christ of Latter-day Saints, 1880 United States Federal Census, (Name: Online publication - Provo, UT, USA: Ancestry.com Operations Inc, 2010. 1880 U.S. Census Index provided by The Church of Jesus Christ of Latter-day Saints © Copyright 1999 Intellectual Reserve, Inc. All rights reserved. All use is subject to the limited;), Year: 1880; Census Place: Adams, Berkshire, Massachusetts; Roll: 521; Family History Film: 1254521; Page: 108B; Enumeration District: 047; Image: 0218.
Record for Joseph Montgomery
http://search.ancestry.com/cgi-bin/sse.dll?db=1880usfedcen&h=20897998&indiv=try
- [S612] Ancestry.com, 1900 United States Federal Census, (Name: Online publication - Provo, UT, USA: Ancestry.com Operations Inc, 2004.Original data - United States of America, Bureau of the Census. Twelfth Census of the United States, 1900. Washington, D.C.: National Archives and Records Administration, 1900. T623, 18;), Year: 1900; Census Place: Adams, Berkshire, Massachusetts; Roll: 631; Page: 11B; Enumeration District: 0022; FHL microfilm: 1240631.
Record for Jos* Montgomery
http://search.ancestry.com/cgi-bin/sse.dll?db=1900usfedcen&h=22538604&indiv=try
- [S1764] Ancestry.com, Massachusetts, Marriage Records, 1840-1915, (Name: Ancestry.com Operations, Inc.; Location: Provo, UT, USA; Date: 2013;).
Record for Cherrie M Montgomery Lond
http://search.ancestry.com/cgi-bin/sse.dll?db=MAMarriageRecords&h=11856408&indiv=try
- [S1411] Ancestry.com, Massachusetts, Town and Vital Records, 1620-1988, (Name: Ancestry.com Operations, Inc.; Location: Provo, UT, USA; Date: 2011;).
Record for Cherrie M Montgomery
http://search.ancestry.com/cgi-bin/sse.dll?db=MATownVital&h=170932318&indiv=try
- [S1764] Ancestry.com, Massachusetts, Marriage Records, 1840-1915, (Name: Ancestry.com Operations, Inc.; Location: Provo, UT, USA; Date: 2013;).
Record for Cherry M Montgomery
http://search.ancestry.com/cgi-bin/sse.dll?db=MAMarriageRecords&h=14538864&indiv=try
- [S2058] Ancestry.com, Vermont, Vital Records, 1720-1908, (Name: Ancestry.com Operations, Inc.; Location: Provo, UT, USA; Date: 2013;).
Record for Percy St Clair
http://search.ancestry.com/cgi-bin/sse.dll?db=VTVitalRecs&h=1167715&indiv=try
- [S204] Ancestry.com, 1910 United States Federal Census, (Name: Ancestry.com Operations Inc; Location: Provo, UT, USA; Date: 2006;), Year: 1910; Census Place: Duluth Ward 2, Saint Louis, Minnesota; Roll: T624_725; Page: 6A; Enumeration District: 0156; FHL microfilm: 1374738.
Record for Persy V St Clair
http://search.ancestry.com/cgi-bin/sse.dll?db=1910USCenIndex&h=13441492&indiv=try
- [S940] Ancestry.com, 1920 United States Federal Census, (Name: Ancestry.com Operations Inc; Location: Provo, UT, USA; Date: 2010;), Year: 1920; Census Place: Los Angeles Assembly District 72, Los Angeles, California; Roll: T625_112; Page: 16B; Enumeration District: 322; Image: 296.
Record for Percival V St Clair
http://search.ancestry.com/cgi-bin/sse.dll?db=1920usfedcen&h=94957119&indiv=try
- [S470] Ancestry.com, California Death Index, 1940-1997, (Name: Ancestry.com Operations Inc; Location: Provo, UT, USA; Date: 2000;), Date: 1945-12-05.
Record for Cherrie M Stclair
http://search.ancestry.com/cgi-bin/sse.dll?db=CAdeath1940&h=7019214&indiv=try
- [S613] Ancestry.com, 1940 United States Federal Census, (Name: Online publication - Provo, UT, USA: Ancestry.com Operations, Inc., 2012.Original data - United States of America, Bureau of the Census. Sixteenth Census of the United States, 1940. Washington, D.C.: National Archives and Records Administration, 1940. T627;), Year: 1940; Census Place: Santa Monica, Los Angeles, California; Roll: T627_256; Page: 9B; Enumeration District: 19-760.
Record for Percival V St Clair
http://search.ancestry.com/cgi-bin/sse.dll?db=1940usfedcen&h=71726817&indiv=try
- [S1764] Ancestry.com, Massachusetts, Marriage Records, 1840-1915, (Name: Ancestry.com Operations, Inc.; Location: Provo, UT, USA; Date: 2013;).
Record for J M Montgomery
http://search.ancestry.com/cgi-bin/sse.dll?db=MAMarriageRecords&h=6298278&indiv=try
|