Robert,
It may seem strange, but that's the standard order and usage for such
individuals, one famous example being Rev. Dr. Martin Luther King Jr.
There might be some standards for order based on when each title was
conferred, but Reverend Doctor appears to be the preferred order based
on a quick
The issue here is that technically "13-14 Apr 1930" is considered by
the program to be the number 13 through the date 14 Apr 1930. If you
change that date to "13 Apr 1930 - 14 Apr 1930" it will sort correctly
(but not display as nicely in reports.) The same issue would arise
even if you specify "13
If you can't locate your original source for the birth date of the
father, it's just as likely that you meant to enter 1877 as it is that
1887 is his actual birth year (or that the cemetery transcription you
derived this from was in error for a similar reason.) I would either
delete the original en
Mary,
The problem you describe here is almost certainly due to the default
location Legacy uses to save its database files (within its own program
folder), which is not the way Microsoft instructs third-party software
vendors to design their software. Instead, user files (such as your family
file)
Actually it's far more likely that the region of NZ she's looking on
the map at simply doesn't have any birds eye views available. The
Birds Eye feature is Microsoft's competition for Google Street View,
and just like GSV it's only available in the places they've sent a
helicopter to take photograp
Adobe is actually fairly good about posting what they call the "known
limitations" of their software, and as Ron mentions virtually all
open-source projects have outstanding trackers and databases with test
methodology to confirm fixes. Obviously if one commercial company is
listing their bugs and
That said, I've reported several bugs via the "Report a Bug"
interface, and never received a single acknowledgment or message that
anyone has even read them, let alone added them to the queue. Perhaps
that's because they were already reported, but since they're still
present in the latest build (an
I would consider FSL to be the repository, and the individual
databases should be sourced based on what they actually are. For
instance, Texas Death Certificates would be sourced under Death
Records > Death Certificates > All countries except... > Created at a
state/provincial level > online images
Shelly,
Here is a direct quote from the Ancestry card catalog listing for the
US WWI Draft registrations:
---
The World War I draft consisted of three separate registrations.
* First Registration. The registration on 5 June 1917, was for men
aged twenty-one to thirty-one—men born between 6 June
Brenda,
I'm not seeing this error in my Descendant Narrative report, either --
if anything, in a few spots where I would expect the source page to
use the "subsequent citation" format it still uses the full source
name (although that might be because my text details differ between
each individual
You say you're running Legacy 7, but have you verified you're running
the latest update? (currently version 7.0.0.86, check the 'Legacy
Home' tab to confirm.) I seem to recall there was an issue with a few
of the reports after one of the interim updates that has since been
corrected.
Steve
On Wed
I would summarize it this way -- whether or not this is a bug (and by
the technical definition of what constitutes a bug, I would say it is
not one), this is a behavior that no one would *ever* want or expect,
and thus it certainly deserves to be changed in a future revision.
Presenting it as user
Judy,
I'm certain this has been the standard behavior since at least version
7.0.0.55 (the one we had for a very long time until this sudden flurry
of updates). I often would realize after pasting a source into a few
spots that I had mistakenly inserted the same detail in a few spots
where it was
Leo,
In the help index for Legacy, search for "Family Tree Maker export" --
details are provided there. Specifics vary slightly between versions
of FTM, but all basically involve exporting a GEDCOM file which you
then import into Legacy.
Cheers,
Steve
Legacy User Group guidelines:
http://w
This is a classic issue of accuracy versus clarity, and there are
people on this group that fall on both sides of the divide, so you'll
probably get a few different opinions on this question. My own take is
that genealogy is an attempt to record events and facts in their
contemporary setting (varia
I know that Legacy automatically populates the NICK field of a GEDCOM
if the given name has a portion in quotation marks. However, the
quoted portion of the name remains in the NAME field as well,
resulting in what I think is rather sloppy-looking data. I've tried
to bypass this by creating a cus
Howard,
Two suggestions to try:
First, in the master source list, verify that you haven't accidentally
checked any of the boxes within the "Show only" section on the right
side (beneath the "Help button"). To display all of your master
sources, every box needs to be un-checked. You might be ina
Jim,
This was a common bug in version 7.0.0.55. It was fixed in the most
recent update (7.0.0.76) so if you update to that, it won't happen
again (and a vast number of other formatting and display bugs have
also been fixed.) If you have the Deluxe version you can update from
within the program b
Even without the Geo-location database, you should be able to revise
short location names by highlighting the offending entry in the Master
Location List and selecting the 'Edit...' button at the bottom. After
revising it and selecting 'Save' you'll get a warning that all entries
using the locatio
More than likely you saw the firewall message after updating because
most firewalls are also designed to detect changes in programs sending
internet requests and flag them (since the change could potentially be
malicious spyware or a virus that modified the program.) Thus, you
might not even remem
Elizabeth,
Have you verified that this isn't a difference between the full and
short location names for this location in the Master Location list?
The reports might be using the short name, while the individual
display typically uses the full name. There are also some location
settings in the Opt
June,
After a quick test I realize you need to follow Sandra's advice about
unlinking the incorrect marriage before attempting this process, or
else your g-g-g-grandfather will also be tagged and deleted (that
tricky "tag everyone in the ancestor chart including spouses" thing!)
Once you have unl
One thing to note with those error messages is that their subject line
has two list names prefixing it: [LegacyUG] and [LegacyUserGroup].
All legitimate group messages are only prefixed by [LegacyUG]. This
implies to me that there's an old (or alternate) list with the name
[LegacyUserGroup] and som
Hi June,
You should be able to do this with advanced tagging and deleting.
These instructions work for Legacy 7 Deluxe -- I can't speak for which
features are available in Legacy 6 or the basic version. You need to
find a tag you aren't using for other purposes (and enable tagging
options from Opt
With all due respect to everyone who keeps arguing that HTML messages
are the bane of the world and the cause of problems on this list, the
two biggest issues with the spam flagging are undoubtedly the
onslaught of repetitive error messages about not being subscribed to
the list (spam heuristics lo
Actually this is definitely a change between build 55 and build 76 --
I was quite surprised to have the the window pop up when I copied a
source to the clipboard and then went to paste it in a new field. I
agree that it's likely to be more useful than detrimental, especially
since you can just hit
Jim,
As far as I can tell, this bug was fixed in the new version (7.0.0.76)
released on Saturday. Beyond that the only way I know of to prevent
the problem is to be very careful when selecting 'Add' versus 'Cite'!
:)
On Mon, Dec 1, 2008 at 1:35 PM, Jim Smith <[EMAIL PROTECTED]> wrote:
> Greeting
I have neither of those problems here, but there was an issue with the
location map occasionally not displaying properly in the prior
version, but it's not due to a bug in Legacy itself. The problem, as
far as I understand it, is that the connection to the Microsoft
Virtual Earth server occasionall
The thing I don't like about the "Book, authored (reprint) > Author
Known > Online Images" option mentioned previously is that the
template does not include a spot for the original publication
information other than year of original publication. To me, that's
potentially as important to a future r
I ran into this same problem, and decided the best choice was to
consider such books as "Book > Editor known > Basic Format" and
provide Google Books as the repository (if you don't use the
repository feature, then mention in the Text/Comments where you found
it.) The rationale being that you're l
I verified it myself with primary sources.
Hope that helps,
Steve Voght
> On Sat, Nov 22, 2008 at 6:04 AM, Arnold Sprague <[EMAIL PROTECTED]> wrote:
>>
>> I gathered some new information on my Strong ancestors from the website of
>> The Strong Family Association of Am
ed by
other genealogists, etc.) Hopefully they list their sources, because
otherwise I wouldn't lend much credence to what's listed there until I
verified it myself with primary sources.
Hope that helps,
Steve Voght
On Sat, Nov 22, 2008 at 6:04 AM, Arnold Sprague <[EMAIL PROTECTED]>
I have to agree with William -- in this case the index was explicitly
created by Ancestry. True, they used some else's data to compile it, but
there is no such thing as a "Nevada Marriage Index" in either Clark County
or the State of Nevada archives... instead there are pieces of this index in
thr
sider a mass-reassignment of identification numbers.
(And as always before doing something major like this, make sure your
backup is up-to-date!)
Cheers,
Steve Voght
Seattle, WA
On Sun, Sep 28, 2008 at 11:13 AM, RICHARD SCHULTHIES
<[EMAIL PROTECTED]> wrote:
> The "double S" is o
Paul, have you looked at the Wine AppDB list? Someone has
successfully installed Legacy 7 using Wine 1.0-rc4 on openSUSE 10.3
(see http://appdb.winehq.org/objectManager.php?sClass=application&iId=3207).
They might have some insight for you.
Also on that list it appears that Legacy 5 works well u
To clarify, since we seem to be going in circles somewhat on this discussion
-- the problem here is NOT with Legacy, but instead has to do with how you
encoded the name and how Microsoft Virtual Earth interprets that data. If
anyone here deserves chiding for not locating a big cemetery in an urban
36 matches
Mail list logo
