To Frode, Carol and Ken and Barbara (who also experienced the same problem)
Got up at 5-00am Australian time and downloaded again,  to desktop, as Ken
suggested - all working fine thank you.
Thank you all for your support.
Anne

-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Ken
McGinnis
Sent: Friday, 25 March 2005 1:34 AM
To: [email protected]
Subject: Re: HELP PLEASE!! RE: [LegacyUG] New Legacy Update - 23 March 2005,
Version 5.0.0.217

Go to our web site http://www.legacyfamilytree.com/DownloadLegacyDeluxe.asp
and 
download and install Legacy.   This will fix things for you.

Thanks

Ken McGinnis
Millennia Corporation
[EMAIL PROTECTED]
http://www.LegacyFamilyTree.com
We are changing the world of genealogy!

----- Original Message ----- 
From: "Anne E Wiltshire" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Thursday, March 24, 2005 1:41 AM
Subject: HELP PLEASE!! RE: [LegacyUG] New Legacy Update - 23 March 2005,
Version 
5.0.0.217


> Hello
> I have just downloaded Legacy as per Ken's instructions and the download
> froze midway through.  When I try to go into Legacy I get the following
> message:
>
> "The Legacy file legacy.lng is the wrong version.
> Expected version 03 Feb 2005 23.25.22
> Your version 23 Mar 2005 18.46.56
> If you are helping with public testing of one of the international
languages
> of Legacy then you should wait for an announcement from your Language's
> mailing list and then use the links in that message or the one's on the
team
> website.  When you install Legacy you should always download a matching
> LegeacyAlt.lng file.  You should never use the menu option within Legacy
to
> check for a legacy update and you should never download any General
Release
> builds announced by Milennia".
>
> I cannot open Legacy at all - I get this message on every occasion.  I
have
> never used anything but the English language and have never been involved
in
> public testing of one of the international languages.
>
> Can this be fixed?
>
> Sincerely
> Anne Wiltshire
>
>
>
>
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Ken
> McGinnis
> Sent: Thursday, 24 March 2005 3:33 PM
> To: [email protected]
> Subject: [LegacyUG] New Legacy Update - 23 March 2005, Version 5.0.0.217
>
> =================================
> New Legacy Update - 23 March 2005,  Version 5.0.0.217
> =================================
>
> Legacy 5.0 Deluxe Edition Users
> ========================
> If you have Legacy 5.0 Deluxe Edition then start Legacy and click on the
> internet icon on the top toolbar.   From the popup menu select "Check for
> Legacy Update" and then click the "Check Now" button (Note: You should
> connect to the internet before you click the Check Now button.)   Legacy
> will check our web site and let you know there is a new build available
and
> you can then click the "Install Now" button.   This will automatically
start
> the update process.
>
> Legacy 5.0 Standard Edition Users
> =========================
> Standard Edition users are required to visit our web site in order to
> download the new update.  Click the Download button on the left.
> http://www.LegacyFamilyTree.com
>
>
> =================================
> 23 March 2005 build
> =================================
> ===========================
> New
> ===========================
> Pedigree Web page creation - Better horizontal ruler grouping between
> sections.
>
> ===========================
> Changed
> ===========================
> RTF report files - The language that you are using in Legacy is now
embedded
> in
> RTF report files so that the correct spelling dictionary will be used when
> loaded into Word.
>
> Multiple Lines of Descent book reports - When a Table of Contents is
> generated
> from an RTF file, each section of the ToC will include the family name for
> that
> section.
>
> ===========================
> Fixed
> ===========================
> Name List Report - Tag 4 - 9 would not print on the first line of the
> report,
> generally ending in an Out of Memory error.  Fixed.
>
> FGS Reports - Parents and Other Spouses that were marked as Private were
> still
> being included on the report.  Fixed.
>
> Calendar reports - The female's surname is used when the "Married names
for
> females" option is selected when the man and woman have a married status
of
> "Unmarried."
>
> FGS Report - When printing to HTML or Text format, the Cause of Death
> information was not output correctly.  Fixed.
>
> Location Report - When Excluding living individuals AND Excluding unused
> locations, locations used by living individuals were being included in the
> report with "This location is not used anywhere."  Fixed.  (They are no
> longer
> included in the report.)
>
> To-Do Clipboard - Pasting a to-do item from the clipboard with a Category
> and
> Locality into a new to-do item from the Add screen and then immediately
> Saving
> it would lose the Category and Locality fields.  Fixed.
>
> To-Do List - Deleting the first item in the list was not refreshing the
> Description tab contents below the list with the next to-do item's
> information.
> Also, the Go To button at the bottom was not be changed.  Fixed.
>
> Potential Problems report - Bad marriage dates were being reported even
when
>
> Date Validation was turned off.  Fixed.
>
> Alternate Names - Given names are now formatted for capitalization in the
> same
> way as given names on the Information screen.
>
> Marriage screen - If you added a spouse from the Marriage Information
screen
> you
> would sometimes get an error 400 when Legacy tried to display the Marriage
> screen again.  Fixed.
>
> Legacy Export - Export to a new Legacy file where the option "Suppress
> details
> for Living People" and "Change name to Living" the AKA names were not
being
> included for non-living individuals.
>
> TempleReady - Prequalifying a child to be sealed to their parents.  We
added
> a
> check to see if the childs work has alreay been performed and if so we
skip
> the
> childs individual qualification checks.
>
> Location Indexes - Some locations were being split into two groups in the
> index.
> Fixed.
>
>
>
>
> Enjoy,
>
> Ken McGinnis
> Millennia Corporation
> [EMAIL PROTECTED]
> http://www.LegacyFamilyTree.com
> We are changing the world of genealogy!
>
>
> Legacy User Group Etiquette guidelines can be found at:
> http://www.LegacyFamilyTree.com/Etiquette.asp
>
> To find past messages, please go to our searchable archives at:
> http://www.mail-archive.com/legacyusergroup%40mail.millenniacorp.com/
>
> To unsubscribe please visit:
> http://www.legacyfamilytree.com/LegacyLists.asp
>
> Legacy User Group Etiquette guidelines can be found at:
> http://www.LegacyFamilyTree.com/Etiquette.asp
>
> To find past messages, please go to our searchable archives at:
> http://www.mail-archive.com/legacyusergroup%40mail.millenniacorp.com/
>
> To unsubscribe please visit:
> http://www.legacyfamilytree.com/LegacyLists.asp
>
>
> 


Legacy User Group Etiquette guidelines can be found at:
http://www.LegacyFamilyTree.com/Etiquette.asp

To find past messages, please go to our searchable archives at:
http://www.mail-archive.com/legacyusergroup%40mail.millenniacorp.com/

To unsubscribe please visit:
http://www.legacyfamilytree.com/LegacyLists.asp

Legacy User Group Etiquette guidelines can be found at:
http://www.LegacyFamilyTree.com/Etiquette.asp

To find past messages, please go to our searchable archives at:
http://www.mail-archive.com/legacyusergroup%40mail.millenniacorp.com/

To unsubscribe please visit:
http://www.legacyfamilytree.com/LegacyLists.asp

Reply via email to