Re: How do you document error messages?

["Ned Bedinger" <doc -at- edwordsmith -dot- com>]

----- Original Message ----- 
From: <mearro -at- msn -dot- com>

> our developers. We're hoping to add more meaningful content to each error

The bottom line is, the error messages may have been written only to prompt
the developer's own deeper knowledge about the problem.


> I've gone through our problem logs and support notes to try to get
> additional info but I've spent too much time for too little results.

Your incremental approach might be a good bet--every time your support staff
has to deal with an error that they don't have information for, log it and
try to get the explanation you need.

BTW, I wonder why errors that require service are not logged?  If the
software doesn't do it, is the support staff too busy?


> Any experiences you could pass on - I'd appreciate.

Ned Bedinger
Ed Wordsmith Technical Communications
http://www.edwordsmith.com



^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

ROBOHELP X5: Featuring Word 2003 support, Content Management, Multi-Author
support, PDF and XML support and much more!
TRY IT TODAY at http://www.macromedia.com/go/techwrl

WEBWORKS FINALDRAFT: New! Document review system for Word and FrameMaker
authors. Automatic browser-based drafts with unlimited reviewers. Full
online discussions -- no Web server needed! http://www.webworks.com/techwr-l 

---
You are currently subscribed to techwr-l as:
archiver -at- techwr-l -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- techwr-l -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot-  Visit
http://www.techwr-l.com/techwhirl/ for more resources and info.