FAMILY-ORIGINS-USERS-L ArchivesArchiver > FAMILY-ORIGINS-USERS > 1998-12 > 0913242191
From: "L.G.Brown" <>
Subject: Re: Perspectives
Date: Wed, 09 Dec 1998 14:23:11 -0800
I used to be one of the those loyal FTM users and supporters. Then I
discovered FOW. And I avoid FTM and WTF's wherever possible. I still
have my FTM and it resides a different computer because of its dominance
over my files. The big thing I have against WFT is the lack of sources.
WFT (BB) overwrites the submitter sources with their Company Logo. As
much as we push for people to include sources, BB takes them away.
I'm very fortunate to have in my possession a WFT that was included in a
store package years ago, which included a direct line of unknown
cousins. It took me forever to learn who the submitter was from BB. I've
had to approach my new cousin several times for his sources, and he kept
telling me it was in the file he submitted to WFT. He was not aware his
35 years of work was overwritten and no longer available. He didn't know
(as many FTM users don't) to embed them in notes instead. He didn't have
a copy of the file, so all that valuable information is now lost.
I bring this up because Paul Burchfield was very instrumental in helping
me through this and other frustrations, and I'm glad to have him aboard
with his new title. I'm sure he is just as attentive to our problems and
concerns about FOW as he was with FTM.
NOW - my big-g-g wish is <g> ...... FOW and FTM be compatible to each
other. A smooth comfortable way to transport FOW files to FTM and visa
versa, to reports, charts, etc without loss of data, and pre-editing of
gedcoms. I know this is a tall order as FTM uses restrictive "facts" and
FOW allows customed events. Two very different animals. Maybe we can
start small, with a wizard that would be user directed telling which
fact equals which event, etc.
Another wish <gg> is to somehow import WFT Gedcoms, via a viewer, to
FOW. Perhaps that means downloading to FTM and then importing it to FOW
via a "FOW/FTM" wizard. Since facts are used differently among FTM
users, perhaps a "safe file" (not in notes) where FOW users could
preview the "facts" first, then assign their event (whether customer or
predefined) and move on.
Lynn in CA
Researching BOCHNICEK * DIEHN * DVORAK * PAZDERA * PETRAN * and NYC
> "Richard D. Chroninger" <>, wrote:
> >I was checking a few of my older Sources and discovered the following 5
> >Comments on 5 of them.
> > @NS21691@@NS21692@
> > @NS118001@
> > @NS201321@
> > @NS193991@
> > @NS207601@
> These are references to notes that came from an FTM gedcom file. FO
> will pick up general notes referenced this way but it will not get notes
> referenced thus from within a source structure in a gedcom file.
> If you still have the gedcom files that these items were imported from,
> you can find those notes there, but the references that were improperly
> transferred into your database, such as @NS207601@ are just worthless
> trash now. They indicate that there were notes in the source comments
> fields in FTM that were not transferred to FO when the gedcom was
> >Actually, FTM probably has as many loyal supporters as FOW does, and we
> >probably need to keep that in mind. I personally know a few of them.
> Here's the chain of events. Banner Blue Software is founded in 1984. It's
> genealogy product, Family Tree Maker, first appears as a DOS product in 1989. In
> 1995 Broderbund Software acquires Banner Blue which continues to operate as a
> separate division. In 1997 Broderbund Software acquires Parsons Technology,
> Paul Burchfield
> The Learning Company