Individual Page


Family
Marriage: Children:
  1. Martha /Merry/: Birth: 1647 in York, York, Maine, USA. Death: 1678 in York, York, Maine, USA

  2. Joseph /Merry/: Birth: 19 DEC 1654 in Hampton, Rockingham, New Hampshire, USA.

  3. Hannah /Merry/: Birth: 29 NOV 1660 in Hampton, Rockingham, New Hampshire, USA. Death: 27 FEB 1758 in Chilmark, Dukes, Massachusetts, USA

  4. Abigail /Merry/: Birth: 19 October 1662 in Tisbury, Dukes County, Massachusetts, USA. Death: 2 May 1741 in Tisbury, Dukes County, Massachusetts, USA

  5. Bathsheba /Merry/: Birth: 16 JUN 1665 in Hampton, Rockingham, New Hampshire, USA. Death: 1765 in Edgartown, Dukes, Massachusetts, USA

  6. Samuel /Merry/: Birth: 16 NOV 1669 in Hampton, Rockingham, New Hampshire, USA. Death: 06 OCT 1727 in Tisbury, Dukes, Massachusetts, USA

  7. John /Merry/: Birth: 28 MAR 1726 in Chilmark, Dukes, Massachusetts, USA. Death: 04 OCT 1771 in Pittsfield, Berkshire, Massachusetts, USA


Sources
1. Title:   Public Member Trees
Page:   Database online.
Publication:   Name: Ancestry.com Operations, Inc.; Location: Provo, UT, USA; Date: 2006;
Author:   Ancestry.com
Name:   www.ancestry.com
Givenname:   www.ancestry.com
RepositoryId:   R-1245221910
Link:   http://www.ancestry.com
2. Title:   U.S., New England Marriages Prior to 1700
Note:   Torry, Clarence A. <i>New England Marriages Prior to 1700</i>. Baltimore, MD, USA: Genealogical Publishing Co., 2004.
Publication:   Name: Ancestry.com Operations Inc; Location: Provo, UT, USA; Date: 2012;
Author:   Ancestry.com
Name:   Ancestry.com
Givenname:   Ancestry.com
RepositoryId:   R-1245221911
3. Title:   Family Data Collection - Individual Records
Page:   Birth year: 1669; Birth city: Marthas Vineyard; Birth state: MA
Publication:   Name: Ancestry.com Operations Inc; Location: Provo, UT, USA; Date: 2000;
Author:   Edmund West, comp.
Name:   Ancestry.com
Givenname:   Ancestry.com
RepositoryId:   R-1245221911
4. Title:   Public Member Trees
Page:   Database online.
Publication:   Name: Ancestry.com Operations, Inc.; Location: Provo, UT, USA; Date: 2006;
Author:   Ancestry.com
Name:   www.ancestry.com
Givenname:   www.ancestry.com
RepositoryId:   R-1245221910
Link:   http://www.ancestry.com
5. Title:   U.S., Find A Grave Index, 1600s-Current
Publication:   Ancestry.com Operations, Inc.
Author:   Ancestry.com
Name:   Ancestry.com
Givenname:   Ancestry.com
RepositoryId:   R-1245221911
6. Title:   U.S., Find A Grave Index, 1600s-Current
Note:   <i>Find A Grave</i>. Find A Grave. http://www.findagrave.com/cgi-bin/fg.cgi.
Publication:   Name: Ancestry.com Operations, Inc.; Location: Provo, UT, USA; Date: 2012;
Author:   Ancestry.com
Name:   Ancestry.com
Givenname:   Ancestry.com
RepositoryId:   R-1245221911
7. Title:   U.S., Find A Grave Index, 1600s-Current
Note:   <i>Find A Grave</i>. Find A Grave. http://www.findagrave.com/cgi-bin/fg.cgi.
Publication:   Name: Ancestry.com Operations, Inc.; Location: Provo, UT, USA; Date: 2012;
Author:   Ancestry.com
Name:   Ancestry.com
Givenname:   Ancestry.com
RepositoryId:   R-1245221911
8. Title:   Public Member Trees
Page:   Database online.
Publication:   Name: Ancestry.com Operations, Inc.; Location: Provo, UT, USA; Date: 2006;
Author:   Ancestry.com
Name:   www.ancestry.com
Givenname:   www.ancestry.com
RepositoryId:   R-1245221910
Link:   http://www.ancestry.com
9. Title:   U.S., Find A Grave Index, 1600s-Current
Note:   <i>Find A Grave</i>. Find A Grave. http://www.findagrave.com/cgi-bin/fg.cgi.
Publication:   Name: Ancestry.com Operations, Inc.; Location: Provo, UT, USA; Date: 2012;
Author:   Ancestry.com
Name:   Ancestry.com
Givenname:   Ancestry.com
RepositoryId:   R-1245221911
10. Title:   Public Member Trees
Page:   Database online.
Publication:   Name: Ancestry.com Operations, Inc.; Location: Provo, UT, USA; Date: 2006;
Author:   Ancestry.com
Name:   www.ancestry.com
Givenname:   www.ancestry.com
RepositoryId:   R-1245221910
Link:   http://www.ancestry.com



RootsWeb.com is NOT responsible for the content of the GEDCOMs uploaded through the WorldConnect Program. The creator of each GEDCOM is solely responsible for its content.