That is why I, and many others, recommend making a permanent choice of using ALL locations, at either 'the time', OR 'now'. I previously used 'now', but when in a ten year period (or so), Sweden, Britian, France etc., changed boundaries from ancient ones to more 'practical', 'modern', 'logical?' I decided that I didn't want to change my records every time a government decided to change itself. But because of this choice, I will forever get messages 'place name is wrong', but I just ignore it in confidence, that it is unfixable quirk of computers. Rich in LA CA --- Tim Rosenlof <[EMAIL PROTECTED]> wrote:
> > There are some errors in Geo and Geo covers only > current > > locations - "it doesn't cover historical > locations" - so the > > two may never match exactly. > > "it doesn't cover historical locations" > Locations, counties change in earlier years, so be > cautious when > entering locations. > > -Tim > > > > > Thanks for using Legacy. > > > > Sherry > > Customer Support > > Millennia Corporation > > [EMAIL PROTECTED] > > http://www.LegacyFamilyTree.com > > > > We are changing the world of genealogy! > > > > When replying to this message, please include all > previous > > correspondence. Thanks. > > > > > > --------Original Message------------- > > > > From: [EMAIL PROTECTED] > > > [mailto:[EMAIL PROTECTED] > On Behalf > > Of David Dearth > > Sent: Saturday, March 22, 2008 9:55 AM > > To: LegacyUserGroup@legacyfamilytree.com > > Subject: [LegacyUG] Geo database bug?? > > > > I've been using Legacy for about four months now. > I am > > constantly being amazed at how packed full of > features this > > program is. I can do so much more with it than my > previous > > software. One of those things is using the Geo > Database. > > Many of my entries for places only have city and > state. I > > have been using the search feature of the Geo > Database, > > filling in the city and state, thereby finding the > proper county. > > > > Yesterday, I did this like I have dozens of times > before: > > searched for Danville, Virginia. The returned > result was > > "Danville, Danville (city), Virginia, USA". When I > try to > > select and use this location, Legacy says "There > was never a > > county by the name of Danville (city) in the state > of > > Virginia.". I have had to bypass this with a > double comma > > (,,) to eliminate the county in this case. > > > > Shouldn't Legacy be able to accept its own search > result? > > (there was only this one result from the search). > A possible bug? > > > > I am using 6.0.0.190 Deluxe. Any suggestions? > > > > Thanks > > Dave Dearth > > > > > > > > > > > > Legacy User Group guidelines: > > http://www.LegacyFamilyTree.com/Etiquette.asp > > Archived messages: > > > http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/ > > Online technical support: > http://www.LegacyFamilyTree.com/Help.asp > > To unsubscribe: > http://www.LegacyFamilyTree.com/LegacyLists.asp > > > > > > > > > > > Legacy User Group guidelines: > http://www.LegacyFamilyTree.com/Etiquette.asp > Archived messages: > > http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/ > Online technical support: > http://www.LegacyFamilyTree.com/Help.asp > To unsubscribe: > http://www.LegacyFamilyTree.com/LegacyLists.asp > > > > Legacy User Group guidelines: http://www.LegacyFamilyTree.com/Etiquette.asp Archived messages: http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/ Online technical support: http://www.LegacyFamilyTree.com/Help.asp To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp
