|
Idenifying twins with FTM
Tue, 25 Apr 2006 03:21:24 GMT
soc.genealogy.computing
previous
Claude...
|
Can anyone advise an efficient way to identify twins (or any multiple
births) when using FTM2006 please? My database is too large to even
contemplate trawling through it 'line by line'.
Paul Blair...
|
FTM doesn't know about multiple births.
Select a person, click Edit. Select Add Fact.
In Type, put Twin, tab down to Place or Description and Type Y (or
anything you like, in fact). Dates don't matter.
Select OK, and now you can tag individuals as a twin. FTM doesn't check
anything, so if you have 3 1/2 sets of twins, it wont see an error.
To get a list (after you've tagged all the twins) just Select Twin where
the condition is Y.
Sadly, there is no way to set up to search for identical birth dates and
tick the box for you.
|
Hugh Watkins...
|
F2 >> index of individuals
click on "birth date " list will be sorted by date
FTM 2006
Hugh W
Paul Blair...
|
Amazing, isn't it? Here we are in the computer age, we can web-search for
topics in microseconds, but to find twins in a list, we have to eyeball
it! No offence, Hugh, but its a pretty chancy way of doing things... ;-)
|
|
Charlie Hoffpauir...
|
Actually, I'm not using FTM any more, but back when I was, I always
kept a "copy" of the database in Access, just for checking things like
this. You can create the Access database by generating a custom report
in FTM containing all the fields that you care to use (whatever you
think might be useful, like names, spouse, b.d., d.d. m.d. etc). Then
copy the report to Excel, and import the Excel table into Access.
Paul Blair...
|
Amazing comment there, CH. There was a time, a few years ago now, where
Excel was my weapon of choice for reprocessing data from Application A
to Application B. It was remarkably friendly to most everything I used,
and was like a kindly uncle in that it had no nasty tricks to ruin your
day. I always thought of it as a non-Microsoft product, because it was
so useful :-)
|
Once in Access, it's pretty easy to generate a query that will give
you exactly what you're looking for, in fact, Paul has already posted
how to do that using the table from Legacy. I tried the Legacy route
as well, but found the custom report to Access much more convenient.
Charlie Hoffpauir
Message board:
Mail list:
DNA project:
|
|
next
|