TMG-L Archives

Archiver > TMG > 2002-02 > 1012601009


From: "Cliff Soderback" <>
Subject: Re: [TMG] New User / Import Question / Database Question
Date: Fri, 1 Feb 2002 15:03:36 -0700
References: <20020131132227.21947.qmail@web13401.mail.yahoo.com> <4.2.2.20020201100804.00af6448@pop3.norton.antivirus>



> >>
> The only other reason that I can think of for not keeping all information
> in a single data set is personal preference or convenience of
> operation. If one or more lines are constantly being updated and being
> distributed from/to other researchers, the user may prefer to keep
separate
> data sets. Now, all lines _could_ be maintained in a single data set and
> any particular line split out to a sub-data set as needed, but the user
may
> _prefer_ to operate with multiple data sets. Of course, a lot may depend
> on the size of the combined data set (say if the family and its lines were
> extremely large).
>
> So as with nearly everything else in TMG, it really comes down to personal
> preference. My preference is a single data set (everything is in one
place
> and I can often find connections and relationships easier this way). But
> circumstances may dictate differently to others.
>
> ----------
> Lee Hoffman/KY

The issue is not whether to have more than one dataset(database), rather
the issue of trying to keep two(or more) databases identical when more
than one person can make entries into the databases.

You will notice that in any computer program that if one person(or program)
opens a file for entry all others are locked out until the file is closed.
This
is to avoid data corruption. There is no way to keep more than one database
identical to another when there is more than one copy of the database open
for entries.

One poster lamented; is there an easy way to get the databases back in
sync, the answer is no, not without reviewing every entry. This is the
reason if more than one person is to make entries into a separate databases
then
the master database should be split to avoid this corruption. One way
is to split the master database into pieces and let each work on his(her)
own
part and reassemble the master database periodically into a read only master
database(this is common in industry), this can be done easily in TMG.

Another way would be allowing the updating of the master database from
a website, but I think that would be beyond the scope of the readers
of the board. A third way is just allow one person to do the entries
in the master database.

Trying to keep more than one database identical is a trap that is not
easy for one to remove him(her)self from. Hopefully bringing up this subject
might keep some folks from falling into this trap.

Cliff Soderback



This thread: