ROOTSMAGIC-USERS-L Archives

Archiver > ROOTSMAGIC-USERS > 2005-02 > 1107904907


From: "Eric Norton" <>
Subject: RE: [RMagic] RM and FTM
Date: Tue, 8 Feb 2005 18:30:46 -0500
In-Reply-To: <00a701c50b98$b8e001f0$6601a8c0@jimsbbb>


Jim,
I understand your problem with data transfer between programs when acting as
a repository for multiple-users. But as you can see, GEDCOM isn't a solution
to your problem. It's just a readily available option. Data availability is
one of the issues I have with some genealogy programs as opposed to RM.
Using proprietary data structures(as FTM does) makes the GEDCOM interaction
almost mandatory for data transfer. However, I can go from Legacy to RM and
back again with no problem and no GEDCOM. Legacy uses Access DB and RM is
FoxPro. I eliminate the middle man by mapping a field to field conversion.
Using GEDCOM as a middleman for import/export is just like opening a word
document and saving as ascii text to bring it into another app. Word has a
few more options than that.
It would be akin to having an option under RM File|Import that allowed you
to select from various programs. Unfortunately, that would require a working
knowledge of their structures. The Master Genealogist website has an SDK
that allows for import from FTM I don't know if it can write to one. I used
to work writing code for data conversions and performing conversions with
off the shelf tools. Often times having to convert from one to another with
multiple intermediate formats along the way. Like wanting to go from FTM to
RM but having to make a Generations file in between.
Individual users shouldn't need to use GEDCOM files for their own work. (I
recall a list discussion on backups made by exporting to GEDCOM files
instead of using the built in Backup function.) And multi-users would be
better off sticking to a non-proprietary data structure. Hence, my push to
get everyone I know using RM. The next step for central repositiories would
be to find a tool that does Genealogical Database Conversions. That too,
could be RM. But it is quite a bit of research/work for the amount of use it
would see and other features would definitely take precedence. Should we ask
Bruce to supply a hook into the RM program and a tiny SDK info package and
see if some of the coders on the list would like to create an Import/Export
filter add-on, in effect removing the need for GEDCOM and its inherent
instability?

My original statement ---
> (any Genealogy program) should be used with as little interaction
> with GEDCOM files as possible.
--- still stands, unfortunately for you, as a Central Site, 'little...as
possible' means persistantly. Your ideal situation would be as few formats
used as possible by your users, preferably non-proprietary, and a central
program that can import and export directly to and from those formats
avoiding the middle step of a GEDCOM.

I'll do some investigation into various conversion tools (like DataJunction)
to see if there is hope in the third party realm. If I find something, I'll
pass it along.

Eric


-----Original Message-----
From: Jim Winfrey [mailto:]
Sent: Saturday, February 05, 2005 10:38 AM
To:
Subject: Re: [RMagic] RM and FTM


Eric,

I wish it was as simple as what you stated. Some of us act as repositories
for groups of researchers and have to be able to import and export gedcoms
to/from several genealogy programs. I use Rootsmagic for all this work
because Bruce understands gedcom and has created the cleanest interface I've
seen. Like Elizabeth said in an earlier post, gedcom is not a static tool.
We, who use it, are forced to learn about and to figure out how to make it
do what we want. The problem I've had with FTM is that RM can handle a FTM
gedcom but FTM can't adequately handle gedcoms from any program I'm aware
of. Evidence of this is that when you export media links via gedcom to FTM,
they are always lost because FTM doesn't recognize links to external data
period.

Jim

This thread: