Many thanks to all who have emailed me off-list. I will continue to be the
"point" person since you have made clear your reluctance to incur the wrath of
those "defenders of the faith" who dismiss our concerns.
CE
From: s...@ihug.co.nz
To: legacyusergroup@LegacyUsers.com
Subject: Re[2]: [LegacyUG] Error in new version
Date: Mon, 7 Sep 2015 05:15:11 +0000
I agree Ron. As I mentioned 2 weeks ago I am discriminated against by not
encountering any bugs, when judging by other comments in this forum, the
program is riddled with bugs to the extent that it barely functions.
. My tree has 5800 names including contact details of most of the 2000
plus living in around 50 different countries. It stretches to 14 generations,
includes media files, and I produce a wide range of Legacy generated reports.
No problems have been encountered other than the lacking feature of same sex
marriages (the workaround for that advised very quickly by Support works well)
and the occasional error report suggesting file maintenance. Just at present I
am working with the program for 10 plus hours a day in preparation for a family
reunion
I wish my recent upgrade to Windows 10 was as straightforward and error free as
Legacy upgrades have been.
cheers from Stan in Wellington
------ Original Message ------
From: "Ronald Bernier" <ronaldbern...@icloud.com>
To: legacyusergroup@LegacyUsers.com
Sent: 7/09/2015 1:25:57 p.m.
Subject: RE: [LegacyUG] Error in new version
CE, since you feel that you repeatedly need to voice your negative anti-legacy
comments, why don’t you just move on and find a program that fits your needs.
Obviously, Legacy is not that program. Are there bugs in Legacy – yes, there
are. However, I challenge you to find any program that doesn’t have bugs. Are
the bugs as serious and as numerous as you try to make everyone think they are
– absolutely not. As David indicated, often times, people come on this list
and complain about a bug that they encountered, when the reality is that the
user was responsible for the issue, not the program.
Ron Bernier
From: CE WOOD [mailto:wood...@msn.com]
Sent: Sunday, September 6, 2015 9:07 PM
To: legacyusergroup@LegacyUsers.com
Subject: RE: [LegacyUG] Error in new version
I am so glad for you, but the bug list is long, well-documented, and makes it
impossible to meet deadlines for reports, conferences, et alia.
Perhaps you have simple needs and small databases, don't have deadlines to be
met that the bugs make impossible, and so forth. A cursory search of the
archive will show you what you have missed and that we are missing. Some of the
bugs have gone uncorrected since Legacy 8 was introduced. Not being able to
earn your living for that long because of old and new bugs? Please.
CE
Date: Sun, 6 Sep 2015 19:41:25 -0500
From: hee...@usit.net
To: legacyusergroup@LegacyUsers.com
Subject: Re: [LegacyUG] Error in new version
Got to agree...this is a great program & I've had few problems over the
years...and those were quickly resolved.
I think they are doing a great job.
Sally
On 9/6/2015 7:25 PM, David Abernathy wrote:
I have been running Lrgacy for msny years and as of yet to have any of these
issues tha have been brought forward. It appears to me that they are mainly do
to ones own doings and poor system maintance.
Sent from my Kindle Fire
In God We Trust
From: CE WOOD mailto:wood...@msn.com
Sent: Sun Sep 06 16:59:37 PDT 2015
To: legacyusergroup@LegacyUsers.com
Subject: RE: [LegacyUG] Error in new version
"It seems every time that the programmers make a change, they mess something
else up. It's as if they don't run through the program and fully test
everything except what they change. Â I retired as a systems developer and if
we had turned out stuff like this, we would be out of a job."Â Â
AMEN!
Â
How sad to ruin the great Legacy reputation this way.
CEÂ
Â
From: genechar...@outlook.com
To: legacyusergroup@LegacyUsers.com
Subject: [LegacyUG] Error in new version
Date: Sun, 6 Sep 2015 16:55:05 -0400
I just loaded version .516 yesterday and already the 1st thing I did brought an
error and shutdown.
I went to change a child status and got a run-time error 3800, 'ChildStatus' is
not an index in this table. Â And, when you click to get out of the error it
shuts down Legacy.
I have never had a problem with this before. It seems every time that the
programmers make a change, they mess something else up. It's as if they don't
run through the program and fully test everything except what they change. Â I
retired as a systems developer and if we had turned out stuff like this, we
would be out of a job.Â
Gene Harris
Legacy User Group guidelines:
http://www.LegacyFamilyTree.com/Etiquette.asp
Archived messages after Nov. 21 2009:
http://www.mail-archive.com/legacyusergroup@legacyusers.com/
Archived messages from old mail server - before Nov. 21 2009:
http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/
Online technical support: http://support.legacyfamilytree.com
Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) and on our
blog (http://news.LegacyFamilyTree.com).
To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp
