Re: Document the detritus?

[brian_das -at- hotmail -dot- com]

Hi John,

I suggest investigating exactly what the "detritus" is. 

It could be junk left over from testing. But many systems create, alter
and drop tables dynamically, often using login names and timestamps to
give the tables unique names. Systems that stick closely to the relational
model are especially likely to have wacky-looking objects in them.

If those tables are just junk, then by all means bring it to the attention
of the database owner. Chat with him or her, or include a clear statement
of scope in your project plan.

If the tables aren't junk, your job is to determine what system events
created those tables, what your audience needs to know about those events,
and write a doc that meets those needs.

Good luck,
Brian

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

Robohelp X3, from eHelp, lets you quickly and easily create 
professional Help systems for all your Windows and Web-based 
applications, including Net. 

Order RoboHelp X3 in May and receive a $100 mail-in rebate, PLUS
free RoboScreenCapture and WebHelp Merge Module. 
 
Order RoboHelp today: http://www.ehelp.com/techwr-l

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