Great example of how to use the PNA as a tool. That is its intent. I do essentially the same thing. When I come across something which doesn't make sense to resolve, I leave it. As an example, I have a lady who documentation says she was born in Kemp, Texas. I tried to resolve it, the problem is there are two counties with a town named Kemp. I have nothing to indicate which of the two counties is correct so I just left it as Kemp, Texas unresolved so I will keep looking for more definitive documentation. BJ On 3/28/2015 12:03 PM, John Okerson via wrote: > I have listened for a good long while on this topic. When I converted from > FTM 16 to FTM 2012, I had a very large list of place names, many of which > were not recognized. I was able to rid my database of about 50% by using > the PNA. I do it differently than most, but I am happy with it. The BIG > thing the several hundred hours of work did for me was eliminate spelling > errors and items placed in location when I feel they belong. I had multiple > entries which meant the same place and many where a misspelling crept in. > > The net result is that my list of places is now completely recognized. > Thus, as I work on the database, if I make a misteak - spelling > intentional - then it is easy enough for the PNA to point it out to me > before I post to Ancestry. > > That is how I work it. > > John Okerson > Lakeland, TN > > ********************************** > List information page > http://lists.rootsweb.com/index/other/Software/FTM-TECH.html > > ------------------------------- > To unsubscribe from the list, please send an email to FTM-TECH-request@rootsweb.com with the word 'unsubscribe' without the quotes in the subject and the body of the message >