Jennifer, Jim is correct in that the four principle events do not support a description field. If you have an Alternate Death with the "Local site field" in the description and you want to swap the Alt Death with the main Death, whatever is in the description will now be a part of the Swapped Death information. That is why I stick to the Address field for Hospitals, AFB, Churches, and other buildings. Cemeteries are the only thing I incorporate in the Location list, but I do not use a comma. It is part of the City or County, ie, Austin in Assumtion Cemetery, Travis County, Texas, USA The GeoDatabase does not like this, though, so I never try to use it with Cemetery locations. I am currently putting all Cemeteries in my Event Addresses. Physical addresses for even rural cemeteries is easy using Google Maps http://maps.google.com/ Just type in the decimal format of the latitude and longitude of the cemetery like 34.1903, -118.36 in the Google map search field and it will produce a map with streets and or county roads, with a map, satellite or hybrid view option. I then select the "LINK to This Page" then copy the webste address and paste it into the Homepage part of the address field. If Findagrave.com has a map of the cemetery I opaste that webaddress in the Homepage button. I then have a map address that will print on reports when I have the Event Address Option selected in Reports. Anyone seeing my reports can then see exactly where the Cemetery is (or Church, Hospital, etc, - Street address, city, State typed into Google maps produces a map also). This can be a time consuming task if you have a lot of addresses. But genealogy is a time consuming hobby, yes?
Having the Findagrave.com web address for the cemetery is also good thing, because I can Show list for the Cemetery Address and print a list for every one using that Cemetery so that I can later submit their burials to the findagrave.com listing if they are not shown in that findagrave listing. The Address Field is the best current method Legacy has as an alternative to the local site field. It works for me. I see no need for Legacy to create a local site field, that would be redundant because a local site field is nothing more than an address. Cemeteries are an exception, because they often do not have mailing addresses like Churches and Hospitals. After all, who is going to read the mail at a cemetery! Matt -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jennifer Crockett Sent: Saturday, September 24, 2005 8:33 PM To: [email protected] Subject: RE: FW: [LegacyUG] Local site field How would this work with the standard birth, baptism, death and burial events? It is in these events that I most want the local site field. By the way, I think the "little thought" you mention is a bit of an understatement. This topic comes up recurrently, and to my mind, the inclusion of a local site field would leave us to get on with our research without trying to tweak the program. Jennifer -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Matt Henderson Sent: Sunday, 25 September 2005 2:53 AM To: [email protected] Subject: RE: FW: [LegacyUG] Local site field It seems the best solution without a new version would be to tweak a current field, such as the Description Field in an Event. Using this field for an address works, and it can be searched for in the DETAILED SEARCH feature, and all individuals can be tagged if needed. This is a current and available solution. It seems that Legacy is already capable of doing what many seem to be wishing it could do, with only a little thought. Matt -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jim Winfrey Sent: Saturday, September 24, 2005 11:10 AM To: [email protected] Subject: Re: FW: [LegacyUG] Local site field On 9/24/05, Keith Bage <[EMAIL PROTECTED]> wrote: > Jim, > > This is why I don't understand the request. I you surround parts of > your address with [[ ]] then it will not print. However if you do at > somepoint want them to print you can check the option to print private > comments and remove the [[ ]]. Try that for 200 people and it will answer the question. Remember, I want the option of printing EITHER the Local Site or the Local Site with its full address. A toggle would allow us to print the top line of the address (usually the Local Site) for event addresses, or to print the complete address. > > In addition the notion that using these methods mess up the address > list you should note you have the option to show only event addresses, > mailing list addresses, repository addresses or ALL addresses. So this > keeps the list tidy. > > Also I'd like to know how the "Local site field" exports. My experience is limited to TMG and Genbox. TMG and Genbox have a Local Site field, They merge this with the Place before exporting to ged so it works well. There is another advantage to a Local Site field. You can click on the one occurrence of a particular place and Show List will show you people from all the hospitals, cemeteries, etc. Makes editing much simpler. > > My only beef with the event addresses is I'd like an option to print > them in front of my locations, therefore making the location appear > longer. > > > > Keith Bage > BAGE One Name Study (GOONS registered # 4451) > > > > P. S. Check out Legacy Family Tree today! > This full featured genealogy program can be downloaded FREE at > http://www.LegacyFamilyTree.com/Index.asp?mid=5917ADi > > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Jim > Winfrey > Sent: 24 September 2005 15:42 > To: [email protected] > Subject: Re: FW: [LegacyUG] Local site field > > Matt, > > I think the issue is that sometimes I want to print the address > details and sometimes I only want to print the local site name the > address is for. Presently in Legacy it's all or nothing. If I use > the event addresses (which I do) and select print addresses for ANY > report, I get the entire address. I would like to simply see an > option to print the addressee (local site) or the entire address. This > would meet my needs best. > > Jim Legacy User Group Etiquette guidelines can be found at: http://www.LegacyFamilyTree.com/Etiquette.asp To find past messages, please go to our searchable archives at: http://www.mail-archive.com/legacyusergroup%40mail.millenniacorp.com/ To unsubscribe please visit: http://www.legacyfamilytree.com/LegacyLists.asp Legacy User Group Etiquette guidelines can be found at: http://www.LegacyFamilyTree.com/Etiquette.asp To find past messages, please go to our searchable archives at: http://www.mail-archive.com/legacyusergroup%40mail.millenniacorp.com/ To unsubscribe please visit: http://www.legacyfamilytree.com/LegacyLists.asp
