I followed your instructions but I am still prompted to enter a password and I cannot get the update without the password.
Ken Roberts Gig Harbor, WA ----- Original Message ----- From: "Rob Weiss" <[EMAIL PROTECTED]> To: <[email protected]> Sent: Wednesday, March 23, 2005 9:50 PM Subject: Re: [LegacyUG] New Legacy Update - 23 March 2005, Version 5.0.0.217 > Thanks guys! That's quite a haul! > > Rob > > > On Wed, 23 Mar 2005 22:33:08 -0700, Ken McGinnis > <[EMAIL PROTECTED]> wrote: > > ================================= > > 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
