<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML xmlns="http://www.w3.org/TR/REC-html40" xmlns:v = "urn:schemas-microsoft-com:vml" xmlns:o = "urn:schemas-microsoft-com:office:office" xmlns:w = "urn:schemas-microsoft-com:office:word" xmlns:m = "http://schemas.microsoft.com/office/2004/12/omml"><HEAD> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii"> <TITLE>Message</TITLE> <META content="MSHTML 6.00.6000.16981" name=GENERATOR> <STYLE>@font-face { font-family: Cambria Math; } @font-face { font-family: Calibri; } @font-face { font-family: Tahoma; } @page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.0in 1.0in 1.0in; } P.MsoNormal { FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman","serif" } LI.MsoNormal { FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman","serif" } DIV.MsoNormal { FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman","serif" } A:link { COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99 } SPAN.MsoHyperlink { COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99 } A:visited { COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99 } SPAN.MsoHyperlinkFollowed { COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99 } SPAN.EmailStyle17 { COLOR: #1f497d; FONT-FAMILY: "Calibri","sans-serif"; mso-style-type: personal-reply } .MsoChpDefault { mso-style-type: export-only } DIV.Section1 { page: Section1 } </STYLE> </HEAD> <BODY lang=EN-US vLink=purple link=blue> <DIV><SPAN class=855002119-02032010><FONT face=Arial color=#0000ff>It also may be a deterrent to future research.  As an example, A researcher may be looking in WV records when the information they seek is in the VA archives; or they search Berkeley County records when they should be looking in Frederick County.</FONT></SPAN></DIV> <DIV><SPAN class=855002119-02032010><FONT face=Arial color=#0000ff></FONT></SPAN> </DIV> <DIV><SPAN class=855002119-02032010><FONT face=Arial color=#0000ff>Wanda Samek</FONT></SPAN></DIV> <DIV><SPAN class=855002119-02032010><FONT face=Arial color=#0000ff></FONT></SPAN> </DIV> <BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px"> <DIV></DIV> <DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left><FONT face=Tahoma size=2>-----Original Message-----<BR><B>From:</B> apgpubliclist-bounces@apgen.org [mailto:apgpubliclist-bounces@apgen.org] <B>On Behalf Of </B>Jeff Pauley<BR><B>Sent:</B> Tuesday, March 02, 2010 10:43 AM<BR><B>To:</B> 'Renee Zamora'; 'APG Public List'<BR><B>Subject:</B> RE: [APG Public List] Historical vs Current Name Places<BR><BR></FONT></DIV> <DIV class=Section1> <P class=MsoNormal><SPAN style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'">I also favor using the location name as it was then. Many of my ancestors were in the area of Virginia that became West Virginia and I record all pre-1863 locations as Virginia. While it does make FTM a little crazy when I do this, it certainly accepts the override to the default WV. It just makes no sense to me to list a current name for a place when that name was not appropriate in that time period. This is also the practice I use for client research documents with a notation stating so.<o:p></o:p></SPAN></P> <P class=MsoNormal><SPAN style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'"><o:p> </o:p></SPAN></P> <P class=MsoNormal><SPAN style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'">Jeff Pauley<o:p></o:p></SPAN></P> <P class=MsoNormal><SPAN style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'">Pacific Pointe Genealogy Service<o:p></o:p></SPAN></P> <P class=MsoNormal><SPAN style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'">Goodview, VA<o:p></o:p></SPAN></P> <P class=MsoNormal><SPAN style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'"><o:p> </o:p></SPAN></P> <P class=MsoNormal><SPAN style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'"><o:p> </o:p></SPAN></P> <DIV style="BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; PADDING-TOP: 3pt; BORDER-BOTTOM: medium none"> <P class=MsoNormal><B><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif'">From:</SPAN></B><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif'"> Renee Zamora [mailto:harrisena@gmail.com] <BR><B>Sent:</B> Monday, March 01, 2010 11:25 PM<BR><B>To:</B> APG Public List<BR><B>Subject:</B> [APG Public List] Historical vs Current Name Places<o:p></o:p></SPAN></P></DIV> <P class=MsoNormal><o:p> </o:p></P> <DIV> <P class=MsoNormal>I have a personal question and wondering if I could get a feel for how others do this.  In the past I recorded name places based on where they were located currently.  Simply because it was easy to lookup.  Then I started to put the historical places based on the event's time frame.  Now my database has part current and historical name places, simple because I never transferred everything over.<o:p></o:p></P></DIV> <DIV> <P class=MsoNormal><o:p> </o:p></P></DIV> <DIV> <P class=MsoNormal>Since starting to use new FamilySearch I see that they are trying to record places as they are known currently.  Should I follow and change everything in my database to reflect it's current location?  I could record a place currently as "Queensbury, Warren, New York, United States" and then in event notes put formerly "Washington County" to reflect the historical event. Then in the individual summary it will note the change historically.<o:p></o:p></P></DIV> <DIV> <P class=MsoNormal><o:p> </o:p></P></DIV> <DIV> <P class=MsoNormal>The benefit of doing this would help me keep my place list neat in my database.  I just wanted to know how others are handling this, and the pros and cons of each way.<o:p></o:p></P></DIV> <DIV> <P class=MsoNormal><BR>Thanks!<o:p></o:p></P></DIV> <P class=MsoNormal><BR clear=all>Renee Zamora<BR><A href="http://www.harrisena.com">www.harrisena.com</A> <o:p></o:p></P></DIV></BLOCKQUOTE></BODY></HTML>