Thanks to all who replied regarding my problem. I suspect it may be a
compression issue as most of you have suggested. I see same problem on 2
computers. a desktop with XP and a laptop with vista. Neither has a working
photo editor now. The desktop had problems and had to be restored to
original so
Seems to me you need Legacy to be a seer, or interpreter - exactly what
databases can't be by the nature of their assembly. Making disparate
assumptions runs against the inherent nature of computerisation, and my
thought would that the computer, in attempting to make such comparisons and
conclusion
I had the same problem. It has been reported and Sherry says that the
fix will be part of the next update.
Cross your fingers,
--
- Christina Hruška
--And the Dragon Grins...
On Sun, Oct 5, 2008 at 12:22 PM, Margaret E Ullman <[EMAIL PROTECTED]> wrote:
> I'm having trouble importing source
I never never do enter a female under her married name! What I am talking
about is if I add a child to a set of parents and her name is Ann Smith. I
have her married to a man named Joe but I don't know what his last name is.
Somewhere else in my database I have a Joe Jenkins married to a woman
I'm having trouble importing sources from one family file to another. (using
ver. 7.0.0.55) I was able to import locations with no problem. When I try
importing sources, I receive Error #3265. I followed the instructions for
correcting that error. Then tried again--same result. Is there a bug o
Michele,
"I suppose I could check the name list every time I add someone but I might
not catch females that I have in my database under their maiden or married
name and I am adding the other."
I would recommend that you NEVER NEVER NEVER enter a female under her
married name. Females should onl
Dennis,
We are in agreement that only a SELECT clause would be required, but I was
thinking more in terms of my experience that multi-duplicated (if that's
English!) names are common within families. To sort these out would take the
user time, especially in one-name sites.
As you say, it does
I am a long time Legacy user who also wishes this were available: it is my
single biggest "wish list" item. I have used another program where there was a
built in check when a new person was added, and it and didn't seem to be a
resource hog. Even if all it did was bring up a list of people w
On Sun, 5 Oct 2008 15:00:48 +0100, ronald ferguson <[EMAIL PROTECTED]>
wrote:
>I certainly hope not. Have you thought about how long it would take for Legacy
>to check the whole of the database for every entry, and then the additional
>work for the user in having to approve or otherwise, again,
Michele,
I certainly hope not. Have you thought about how long it would take for Legacy
to check the whole of the database for every entry, and then the additional
work for the user in having to approve or otherwise, again, for every entry.
For larger databases life would become next to imposs
I would like it if Legacy would warn you when you add a new person if there
are any possible duplicates in your file. I suppose I could check the name
list every time I add someone but I might not catch females that I have in
my database under their maiden or married name and I am adding the o
11 matches
Mail list logo
