The manual is actually pretty good when it's accurate. The problem is that when a release schedule is hustled, the documentation is the first casualty. In order to have a printed manual, the text must be finished and 'ready to ship' (to the printer) at least a month before it needs to be added to the package. Add to that the lead time to get the package manufactured and assembled, and you've got the manual representing the state of the program a good two months before it shipped, plus whatever wishful thinking was still not functional yet. In Poser's case, those two months were crucial. There are undocumented functions, and functions documented in classic computerese (you know, like "Use File > Save to save files" and "The Hierarchy Editor edits hierarachies." And inaccuracies, of course, which would have been caught if an editor had actually checked the program against the documentation. When documentation is weak, there is a whole string of culprits to examine, and the trail usually leads to the market bigwig who said, "Futch the documentation; I want revenue."