TMG-L Archives

Archiver > TMG > 2003-09 > 1062445171


From: Terry Reigel <>
Subject: Re: [TMG] Project vs dataset
Date: Mon, 1 Sep 2003 15:39:31 -0400
In-Reply-To: <1d5.10145533.2c84eae2@aol.com>


On Mon, 1 Sep 2003 14:33:06 EDT, wrote:

> Terry,
> First, the flags are the same for each database. The new
> one may not have as many as my main one, but those that
> it has are the same with the same values. What happened
> was that the values were set differently. People in my
> main database "died young" when they died at 98; some
> died in the Civil War when they lived in the 1900's.

Are you saying:
1) People had different values after the merge than they did before?
They shouldn't, and if they do it's a bug.

2) The values for two flags with the same name had different meaning
in the two datasets? If so, you need to fix that. The best way is
probably to change the name of one flag or the other.

3) People from a dataset without a specific flag ended up with a
strange value after the merge? They will be assigned the default
(first) value of that flag. If that's not appropriate, the best
solution is probably to change the order of the list of values before
the merge so that the people in the other dataset will get the most
appropriate value. You will probably have to fix some of them anyway.


> The next thing that happened was that my accents were all
> changed. My Civil War death became Interim2 with the
> same values as the old Civil War flag. Many of the others
> were replaced by "Problem" flags and "Interim" flags.
> All the colors were changed.

Are you talking about merging datasets here, or projects? Accents
apply to Projects, not to datasets. Merging datasets within a project
shouldn't change them. Maybe I'm missing something here. Could you
explain more what was going on? Are you importing rather than merging?


> My next problem was that I couldn't merge the sources.
> There were no citations for the duplicated set, but when
> I tried to merge or delete them, I was given a "Fatal
> Error Exception Code=C0000005 Called from
> FRMMERGERS.MMergersources Line/24."

This means the program has taken a wrong turn someplace. I just tried
it in a small test project and it works fine. There may be something
about your project it doesn't like. You say your database is large,
which would make it difficult to send to someone to test.

> I tried to import the second database of descendants and
> merge the common ancestor, but I wasn't allowed by the
> program.

You cannot merge two people in different datasets. So if you imported,
but didn't merge the resulting datasets, you will not be able to merge
the people who are in different datasets.

> I tried to copy the person, but I got all the
> above problems.

You got the above problems while trying to merge datasets, or trying
to copy people? Or both? I'm now confused about what you were doing
when you had these problems.

> I do have an idea about the source of the problem though
> and perhaps you can tell me if it is probably what is
> going on. My database is very large and my computer VERY
> full. I am wondering if I just don't have memory enough
> for the computer to sort, merge and delete. Does that
> make sense with the kind of errors I am getting?

Perhaps. But except for the Fatal Exception Code, which is clearly an
error, I'm not sure yet anything is actually doing other than what it
should. We need to better understand what you were doing and what you
saw to know for sure.

Terry



This thread: