I hope I’m not extending this discussion more than necessary, but it is very interesting, but now I am somewhat confused about what I should do; I’m pretty new at using Legacy, and haven’t ventured out into sorting/finding/making reports yet, nor am I very tech saavy; but now I am concerned about what will or will not show up in a report that I send along to someone else; I would be sending this (hopefully) as GEDCOM to others mostly outside USA, but after seeing all this discussion I may need to print/send manually. ..I have these questions, please clarify if I am understanding the viewpoints expressed correctly, likely 2 slightly different topics, but hopefully make sense:
1. Regarding the cemetery documentation itself; if we are to put commas in “4” places, as Sherry suggests, what is the purpose of the dash instead of the comma, e.g. if you have cemetery, town, county, state, and ?? country; is it to “limit” the sorting to 4 fields? Or is it just to tie the cemetery location to the town for geographical purposes? What happens if there are 5 fields? Does the program look at the two words with the dash as one word? And what “types” of reports does this make a difference in? Does it make a difference in a GEDCOM output? And then how do others “outside” USA suggest writing the pattern? If I were to use the “commas” similarly for foreign addresses, would the “sort” function work the same way? Or is the program “coded” only for USA so that e.g. the second “word” is the town, third “word” is state/county, etc? 2. I see the back and forth preferences of listing cemetery in Events field vs. burial location line. I have been putting cemetery in location line because it made more sense to me, but if it’s better to put in “events” field, some say that WON’T show up in a report? Is that true, and in what cases? It does seem like more work to list in the events section, and I’m confused now about what are the benefits of doing so. . .if someone could explain more clearly why it’s better? In other words, is it only a gedcom issue, or does it have to do with certain TYPES of reports, or sorting? If it means I have to manually “adjust”/ edit that particular info like in a text file to send someone, just to make sure they get the information, then I want to do it another way, which would be. . . .??? 3. And then, the events issue, when transferring to a gedcom, do “other” events such as census listings, or occupations, get excluded as well? If so, what can be done about this, besides manually editing the info in a word processing program? I have thousands of people in my database and there has got to be an easier way. 4. What happens in reports if the additional cemetery address location is listed into the text/comment area under “source” documentation of the cemetery itself? I’m assuming that means no geographical mapping functionality, but what about for reports or gedcom? Thanks so much for patience with these questions! Pam From: Sherry/Support [mailto:she...@legacyfamilytree.com] Sent: Saturday, November 23, 2013 12:43 PM To: LegacyUserGroup@LegacyUsers.com Subject: Re: [LegacyUG] Burial Location as a Cemetery Event The reason why I recommend *not* to put the cemetery name in the location field is that it messes up sorts in the Master Location List as well as the "Expand/Contraction Location Parts" tool if you have entered it as Riverview Cemetery, South Bend, St. Joseph, Indiana, United States Some people who want the cemetery in the location field will enter it as Riverview Cemetery-South Bend, St. Joseph, Indiana, United States in order to retain the 4-place settings that are required for the proper sort and Expand/Contract. Geoff uses the Burial Address but I don't find that flexible enough for reports. We realize that the 4-place governmental jurisdictions don't always apply for locations outside of the US. In my file, I have utilized commas to keep the four places so I can do a good sort or use the Expand/Contract. Sincerely, Sherry Technical Support Legacy Family Tree On Sat, Nov 23, 2013 at 12:26 PM, singhals <singh...@erols.com> wrote: Sherry's probably in the majority, but FMPOV "Wrong" is highly subjective, and if it floats your boat or fills some need you have, put the cemetery name into the burial place field. I'd've personally thought that was where it should go anyway. Cheryl COLETTE SIKES wrote: > Good Day All > Two weeks ago, I finally purchased Legacy Deluxe Edition > (and about died waiting for the password code to arrive so I > could download it without the CD!). I have had my tree on > Ancestry for 13 years and did purchase Family Tree Maker > about 2 years ago so I could sync my tree but for whatever > reason mine wouldn't work after the first sync and they > weren't able to resolve my problem so I just gave up. I > wanted so bad to create reports and have been on the mailing > list for Legacy for a long time, so I finally jumped in! I'm > so glad I did! Needless to say, I have lots of cleaning up > to do - especially with locations. > I have been able to answer many of my questions by searching > through the archives but I still have one issue that I > haven't been able to resolve. I would like a report of > burial locations - show me everyone who is buried in Cotton > Valley Cemetery, Cotton Valley, Webster, Louisiana, USA. If > I leave the cemetery name in the buried field, then it shows > up in the location report as I want it - even if it is wrong > because the location should be city, parish/county, state, > country. > I found Sherry's/Support message from 22 Nov 2010 that > states she enters the burial information as a Cemetery Event > (and her words - and you can do so much more with the Events > Report). So when I changed 3 family members burial location > to a Cemetery Event and created the report, it shows up as > Alpha Name of the individuals and not grouped together by > cemetery. > Is there any way I can see everyone who is buried at a > certain cemetery grouped together? > Thanks so much for any assistance you can provide to this > newbie! I look forward to many happy hours with Legacy! > Colette Alfred-Sikes 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
