Byron Some time ago I remember having problems with indexing in reports quite suddenly not showing the birth and death years on names for about half those indexed. Despite sending reproducible samples to Legacy I got nowhere, and about a week later I changed back to a previous value a totally unrelated report option, and suddenly all the birth and death years reappeared. In other words, there was a bug where the two options supposedly independent weren't.
It's possible you are encountering something similar, so I'm suggesting trying to recall something else you have changed, and changing it back. In my case the unrelated option MIGHT have been the "Private" options, but I regret, I now cannot recall what it was. If it was, fiddling with birth and death years on names in the index MAY fix your problem. Peter --------------------------------------------------------- Peter Haughton [EMAIL PROTECTED] --------------------------------------------------------- |> -----Original Message----- |> From: [EMAIL PROTECTED] |> [mailto:[EMAIL PROTECTED] Behalf Of Byron |> Schafbuch |> Sent: Monday 20 March 2006 5:39 am |> To: [email protected] |> Subject: Re: [LegacyUG] Privacy setting bug |> Pardon my late response to previous help-have been out of town. |> |> OK, to further define basics of the problem. |> I am currently using Standard Edition of Legacy, version 6.0.0.83, have |> used the privacy override features in the various options menus for reports |> and web creations in a variety of ways for different reports and web pages I |> make for people for some time now and have a web site up for 2 years. I |> have a number of people that would rather their name and information be held |> as 'private' on my reports and web pages, and this feature HAD worked in the |> past for my web pages that were created using V5.0. People tagged as |> private were reported as 'Private', and their information hidden. Sometime |> during version 5, a later update of my web pages, resulted in those tagged |> as 'private', were no longer kept private, but rather all their names and |> information went public. When another 'family' member brought it my |> attention, I tried a number of times to 'fix' the problem and regenerate my |> web pages, managed to get the 'private' info problem fixed, but with no luck |> so far regarding 'private' names. I have been forced to remove a majority |> of my web site because of this problem. |> Since then I have upgraded to V6, kept up with latest releases, deleted |> the .usr files, deleted and reset the various .rs*/rf*/wf*, etc setting |> files for report formats and web pages, have uninstalled/installed Legacy, |> deleted, exported/imported to/from gedcom and legacy database files and such |> all to no avail at this point. |> I have always kept up with the Legacy upgrades and love the program for |> its features and sourcing options. But if I can't get this 'privacy' issue |> problem fixed soon, I will be forced to find/use some other program, which |> of those I have looked at so far, suck for integrated features. |> At this point I don't think I have a problem with any corrupted files, |> and am inclined to think I have found a strange problem in Legacy. If |> anyone else can help solve this problem, or offer a reasonable work around, |> will be glad to listen and experiment. Though keeping in mind a database of |> 16000+ makes any manual editing an impossibility. |> |> Thanks All - Byron Enter the drawing for a FREE Legacy Cruise to Alaska or a FREE research trip to Salt Lake's Family History Library. Open to users of Legacy 6 Deluxe. Enter online at http://legacyfamilytree.com/FreeTrip.asp Legacy User Group 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/ For online technical support, please visit http://www.legacyfamilytree.com/Help.asp To unsubscribe please visit: http://www.legacyfamilytree.com/LegacyLists.asp
