TMG-L Archives

Archiver > TMG > 2002-04 > 1017679952


From: "Gene Stuff" <>
Subject: Re: [TMG] OT: how to print out everything in UFT
Date: Mon, 01 Apr 2002 16:52:36 +0000


>From: Collene Pearce <>
>
>>In the past, I've noticed that the most complete "report" in
>UFT is the FGS report. So, I'd like to print EVERY piece of
>data for EVERY person in each of my projects. So, I started
>to do this and realized that UFT will print "ancestor down" or
>"individual, back up the tree", but misses anyone who is not in
>that direct line. Is there a way to get EVERYone??

The FGS report uses "short" dates (not free form) and places and doesn't
print such things as text for the birth events for the children, so beware
of this somewhat. However, if under "family" you choose "all" you will get
all the people.

If you use the "Family Journal" Report, and for your order choose "family"
rather than "descendant" or "reverse register." That should also get you
all the people. However, I don't believe that there is any way to print
"all" the data in UFT. This was one of the criticisms of that package.
Just two examples: Social Security numbers cannot be printed by any report
by program design. I believe research notes and begin and end dates for
places also do not print anywhere. And, if, for example, you wanted to
print source transcripts, you'd have to do that with a source summary
report.

>
>Does anyone have a better suggestion than creating an FGS report
>contiaining every person in every project????

If your dataset is sufficiently small and your patience is sufficiently
large, your task is do-able. However, it seems like there must be a more
efficient way to do this. After all, if a type of information transfers
correctly for 100 people it's unlikely to be transferred incorrectly for the
101st. Software (in general) doesn't make random errors, but rather
systematic ones. Perhaps you could come up with a scheme to check every
"type" of data without checking absolutely every single piece of data. To
do this maybe you could print lots of different types of reports for a
subset of people for which you have intimate knowledge of the correct
"answers" and would readily recognize errors. In addition, check for the
oddities in your data set, like long text entries, odd relationships, etc.
Be sure things print as you expect. Also, be sure to save the UFT software
and your last pre-migration dataset, so if you discover errors later you can
always see how things were before you transfered. I still keep Roots III
for just this reason, though it's been many years since I went back to it.

_________________________________________________________________
Send and receive Hotmail on your mobile device: http://mobile.msn.com

This thread: