I'll just throw in my two cents here...
I went through and customized my database with sentences a while back. The
sentence feature is great and I loved how they read when I used Legacy to
generate a web site (my primary method of communicating my research right
now).
However, for several reasons, I recently decided to go with TNG (The Next
Generation of Genealogy Sitebuilding) for web page creation. Now I'm having
to face the fact that gedcom exports to not carry along the nifty sentences.
Now I'm left with fields that don't always really convey the true picture
without that existing sentence structure.
My point is - if you plan to use Legacy reports and/or Legacy web pages, you
are fine. If you plan to go outside of Legacy for any reason, the current
gedcom vehicle will not carry those sentences with you.
I find that genealogy is an ever-evolving process. I actually love it that
way, but there are always a few bumps along the road.
It's all a personal decision, but something to keep in mind...
Gail Rich Nestor
Smyrna, Georgia, USA
www.roots2buds.net
----- Original Message -----
From: "Elsie Saar" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Tuesday, January 31, 2006 10:12 AM
Subject: Re: [LegacyUG] If-then-else statements - solution; another
sentence question
Dennis, I see your point. I'm not a programmer or an experienced Access
user, just did a few if-then-else statements in Lotus1-2-3 then Excell
while an employee. I reviewed what you said and now understand that I
could put [[none]] in desc and it would read as just a date. Much easier
to form the sentence. But, I sincerely appreciate Don's explanation of
how to use the IF statements and learned a lot.
While we talk about these sentences, I have a question. Do many of you
actually use them. I'm working with them as I clean up my 8200+ location
table. As I clean up an event, I make sure the sentence reads correctly.
Am I wasting my time doing this?
Thanks again for all the stimulating discussion on this list.
Elsie Scharpf Saar
Genealogy research
American: Parks, Avann, Bulson, Soden, Menkens
German: Wienecke, Storz, Scharpf, Saar, Stelzer
----- Original Message -----
From: "Dennis Kowallek" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: January 31, 2006 8:20 AM
Subject: Re: [LegacyUG] If-then-else statements - solution
On Mon, 30 Jan 2006 21:00:14 -0500, "Elsie Saar" <[EMAIL PROTECTED]>
wrote:
I enter None for people who do not have an occupation in the census. I
needed a way to generate the sentence
"He was not employed on 6 May 1930." I didn't want to use an alternate
sentence for everyone, thinking there must be an easier way.
Therefore, following Don's suggestion in the event fields I enter:
eventname = occupation
desc = [[none]]
date = 6 May 1930
The sentence structure for when only the desc and date are filled
becomes
[:IF [Desc] :: [heshe] was employed as [desc] [ondate] :: [heshe] was
not employed [ondate]].[sources][notes]
I don't think you realize that you are NOT exercising the ELSE logic in
the above sentence when you get "He was not employed on 6 May 1930.".
You are actually getting your sentence from the "If only Date filled"
sentence.
Proof...
I created a new event called Test and entered two event sentences...
If only Desc and Date filled:
[:IF [Desc] :: [heshe] was employed as
[desc] [ondate] :: [heshe] was not employed ondate]].[sources][notes]
If only Date filled:
here
I then added the following event:
eventname = test
desc = [[none]]
date = 6 May 1930
The resulting sentence read...
Here
So you are wasting your time creating these complicated sentences.
Dennis M. Kowallek
[EMAIL PROTECTED]
Legacy User Group 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
