> Hmmmm.... We have a process in our product that can take between 3 > to 20 > hours, depending on the size of the data being analyzed.... We've > joked that > my instructions should encourage users to go take a nap, or take
Many moons ago I documented the process for the accounting department when they switched from a home-grown accounting process to an Oracle Financials process (don't shoot the messenger..they were the ones who insisted on running Oracle Financials on a desktop PC). Once everything was setup, you click the command to run. It would then run for 9 hours. Since it was internal documentation, we DID include the suggestion to go home, have a glass of wine, see the kids, then come back 9 hours later. John Posada Senior Technical Writer "They say everyone needs goals. Mine is to live forever. So far, so good." ______________________________________________ Author Help files and create printed documentation with Doc-To-Help. New release adds Team Authoring Support, enhanced Web-based help technology and PDF output. Learn more at www.doctohelp.com/tcp. DOCUMENTATION & TRAINING WEST 07: THE USER EXPERIENCE April 18-21, 2007 ~ Vancouver BC ~ Marriott Pinnacle ~ free city tour 40+ sessions * free workshops * free iPod offer * www.doctrain.com _______________________________________________ Technical Communication Professionals Post a message to the list: email [EMAIL PROTECTED] Subscribe, unsubscribe, archives, account options, list info: http://techcommpros.com/mailman/listinfo/tcp_techcommpros.com Subscribe (email): send a blank message to [EMAIL PROTECTED] Unsubscribe (email): send a blank message to [EMAIL PROTECTED] Need help? Contact [EMAIL PROTECTED] Get the TCP whole experience! http://www.techcommpros.com
