I have never been able to make this work. It says leading commas. My commas could be anywhere in the location.
Anne On 27/02/2014 2:11 PM, Leon Chapman wrote: > Anne: > There is an option on Descendant & Ancestor Book reports to delete one > or more than one leading comma. Check the report options under the > Format tab. > > ___ > Leon Chapman > chap...@gmail.com <mailto:chap...@gmail.com> > ----- > > > On Wed, Feb 26, 2014 at 7:29 PM, Anne Hollingshead > <holl...@melbpc.org.au <mailto:holl...@melbpc.org.au>> wrote: > > I use the multiple comma solution to be able to sort my locations > right down to addresses. > > I use a dash after the town and add the address so that they will > sort well and when I am entering a location it usually > automatically fills in if I have a similar entry. > > This way I can easily make a list for cemetery visits or be > alerted that another family of the same name lives in the sames > street for example. > > All I need is for legacy to provide the option of deleting more > than one comma for reports. I can do this in RTF for some- much > easier to do it in Legacy. > > > Anne > > On 27/02/2014 12:04 PM, CE WOOD wrote: >> You have stepped into a minefield! Legacy Support will emphasize >> their strict structure, quite naturally. >> >> Not even all the United States locations conform to the 4 place >> structure, but that doesn't bother Legacy. >> >> Foreign countries certainly don't. >> >> Because of the problems with Address Locations, many people put >> detail in their locations, using an abbey as a location, using a >> cemetery as a location, et alia. It works beautifully because you >> can always sort Right to Left and find all sites located in the >> same country, county, city, etc. >> >> In your case, enter all the info - city, Twp., county, state. You >> will always be able to find it. >> >> Forget about the inane idea of inserting commas for missing >> counties. That's rigidity that is unnecessary. You will hear >> otherwise from Support, but then..... >> >> As more and more "aliens" use Legacy, they may yet change....... >> >> As for Family Search, don't open that can of worms! >> >> >> >> CE >> ------------------------------------------------------------------------ >> From: tam...@brightok.net <mailto:tam...@brightok.net> >> To: legacyusergroup@LegacyUsers.com >> <mailto:legacyusergroup@LegacyUsers.com> >> Subject: [LegacyUG] Entering info in location field >> Date: Wed, 26 Feb 2014 16:51:32 -0600 >> >> Entering place in the location field. I'm coming from FTM16 to >> Legacy 8. I was wondering if there is a preferred way to enter >> information in the location field. I would like to know how >> others are entering location for census events as well. >> >> I did it this way in FTM for the location field: >> >> Madill, Marshall Co., Oklahoma >> >> For census events I did the reverse: >> >> Oklahoma, Marshall Co., Wills Twp., etc.... >> >> Is there a way it should be done to work with maps? >> >> I have noticed some not listing the Co.,: >> >> Madill, Marshall, Oklahoma >> >> If you put the Country do you use USA or United States? >> >> Thanks, >> >> Tammy >> >> >> >> Legacy User Group guidelines: >> http://www.LegacyFamilyTree.com/Etiquette.asp >> Archived messages after Nov. 21 2009: >> http://www.mail-archive.com/legacyusergroup@legacyusers.com/ >> Archived messages from old mail server - before Nov. 21 2009: >> http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/ >> Online technical support: http://www.LegacyFamilyTree.com/Help.asp >> Follow Legacy on Facebook >> (http://www.facebook.com/LegacyFamilyTree) and on our blog >> (http://news.LegacyFamilyTree.com). >> To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp >> >> >> Legacy User Group guidelines: >> http://www.LegacyFamilyTree.com/Etiquette.asp >> Archived messages after Nov. 21 2009: >> http://www.mail-archive.com/legacyusergroup@legacyusers.com/ >> Archived messages from old mail server - before Nov. 21 2009: >> http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/ >> Online technical support: http://www.LegacyFamilyTree.com/Help.asp >> Follow Legacy on Facebook >> (http://www.facebook.com/LegacyFamilyTree) and on our blog >> (http://news.LegacyFamilyTree.com). >> To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp > > > > Legacy User Group guidelines: > http://www.LegacyFamilyTree.com/Etiquette.asp > Archived messages after Nov. 21 2009: > http://www.mail-archive.com/legacyusergroup@legacyusers.com/ > Archived messages from old mail server - before Nov. 21 2009: > http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/ > Online technical support: http://www.LegacyFamilyTree.com/Help.asp > Follow Legacy on Facebook > (http://www.facebook.com/LegacyFamilyTree) and on our blog > (http://news.LegacyFamilyTree.com). > To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp > > > > > Legacy User Group guidelines: > http://www.LegacyFamilyTree.com/Etiquette.asp > Archived messages after Nov. 21 2009: > http://www.mail-archive.com/legacyusergroup@legacyusers.com/ > Archived messages from old mail server - before Nov. 21 2009: > http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/ > Online technical support: http://www.LegacyFamilyTree.com/Help.asp > Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) > and on our blog (http://news.LegacyFamilyTree.com). > To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp Legacy User Group guidelines: http://www.LegacyFamilyTree.com/Etiquette.asp Archived messages after Nov. 21 2009: http://www.mail-archive.com/legacyusergroup@legacyusers.com/ Archived messages from old mail server - before Nov. 21 2009: http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/ Online technical support: http://www.LegacyFamilyTree.com/Help.asp Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) and on our blog (http://news.LegacyFamilyTree.com). To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp
