I know this is a bit off topic... Our support organization is trying to create a problem determination guide for our product. What I mean is a "scripted" flow chart that they run through to try and isolate (or even fix) a customer's problem. The biggest issue I see with this is that as a product changes over it's lifetime, the contents of this guide will change. In addition, we'll want this to be developed by the support personal as they gain experience with the product, finding new diagnostic procedures and tools. This is likely something built on a hierarchical database with a bunch of questions like, does this work? Does that error occur? Is there this message in a log? Anyone seen this? Any suggestions. --- Wayne Johnson, | There are two kinds of people: Those 3943 Penn Ave. N. | who say to God, "Thy will be done," Minneapolis, MN 55412-1908 | and those to whom God says, "All right, (612) 522-7003 | then, have it your way." --C.S. Lewis __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.mn-linux.org/pipermail/tclug-list/attachments/20071109/eb503f91/attachment-0001.htm