This latest discussion illustrates the need for a comprehensive data element
reference targeted for the User base (not an under-the-hood data
dictionary). If I decide to use the Event Address field of a Census event
instead of a Description field of a Residence event for "123 S. Main St.", I
need to know the system-wide impact of such a change BEFORE I change many
thousands of records. I need to know which reports will be affected as well
as the GEDCOM impact.
I'm not looking for a 5 lb. tome; just a table listing each data element and
where that element is used. Armed with that kind of info, I'm sure I can
make much better use of Legacy than I am now, in addition to saving future
(and unnecessary) headaches.
I haven't bought the User's Manual, I'll admit, so if this type of info is
in the manual, please let me know and I'll buy it tomorrow.
Thanks!
Margaret
----- Original Message -----
From: "Matt Henderson" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Saturday, September 24, 2005 12:52 PM
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
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
--
No virus found in this incoming message.
Checked by AVG Anti-Virus.
Version: 7.0.344 / Virus Database: 267.11.6/111 - Release Date: 9/23/2005
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
