I have been putting my installation of Legacy 3.0 through its paces, trying to see whether any of the several analysis routines have been significantly improved. I was happy to discover, among other things, that the relationship calculator was much more thorough than previously. Several other analyses produced the same results as before. Next I ran the "Potential Problems Report" and, in the event, found several records in my data base that I wished to exclude from the reporting. Since I had forgotten how to handle the exclusion, I went to the "Help" file and learned that control of the exclusion flags was to be found by right-clicking on the individual's tag box or the marriage tag box. Much to my dismay, I found that it doesn't work that way in Legacy 3.0. When I right-click on the individual tag boxes, an instance of the "Advanced Tagging" screen is brought up. This screen contains no mention of the "potential problem" capability. Right-clicking the marriage tag boxes produces a result identical to what happens when I use the regular, left mouse button (i.e., the tag is either set or cleared, as appropriate). I can find no access to the "potential problem" include/exclude flags anywhere in Legacy 3.0. If the access to the "potential problem" flags has been changed in Legacy 3.0, neither the "Help" file nor the printed manual reflects that change. Where did the control for those flags go? While I'm on the subject of the user documentation for Legacy 3.0, I found another residual left over from Legacy 2.0, but this one I managed to figure out on my own. In Legacy 2.0, under the "View" menu was an item that said something like "Trees in this Family File." Selecting that caused your data base to be searched for all the disjoint family trees contained. In Legacy 3.0, documentation notwithstanding, there is no such selection. There is a selection called "Tree Finder ..." which brings up a list of the primary individual in each disjoint tree as of the last time the analysis was run. On that screen is a "refresh" button, which causes the search to be re-done. But that's not what either the "Help" file or the manual says. As I said, I figured this one out, but the user documentation needs to be updated. All things considered, I believe Legacy 3.0 only nails down Millennia's position as the premiere provider in the genealogical arena. Like any full product re-write, there are a few minor blemishes to be smoothed over, but Legacy is still far and away the best there is. Bob Strait
