>>I believe it. Just like I said in another thread a few days ago. There are some things you just can't defend against [code defensively for]. One of which is a stupid user or customer who will not follow instructions. I sent out a 7-page ILLUSTRATED step-by-step set of instructions on unzipping 2 self-extracting files I provided on an accompanying CD and the customer still screwed it up. The default unzip folder was already set for them as well.
>
>Just a thought, without wishing to sound critical, but 7 pages even with pictures seems a bit excessive.
>
>I've found that the longer & more detailed the instructions are, the less likely they are to be read. A bit like CV's (aka resume's) - the longer & more detailed they are, the less likely they are to be thoroughly read, so minimise the chances of getting the job.
>
>Now I keep such instructions brief (preferably less than a page) (still some people screw it up - but less of them).

Mark's right, Len. I've tried both his and your method. Neither works with some users.

I have also guided the 'user', while s/he was setting at the console, using both the printed instructions with pictures, and pointing out how the pictures match the various steps, on each and every step. All to no avail. "I didn't know I had to click on that little folder thingy..." Duh! What did I show you yesterday. Why did I guide your hand with my hand and push your index finger with my finger? (Under my breath: Why am I even doing this? How did you get hired? You too stupid to run a computer.)