Tales From Technical Support Content
During the 1990s, I was training linguists in how to "gloss" texts in a foreign language--that is, to provide an English word under each foreign word that explained its meaning. I discovered one guy who was eager to get started on his own, without training, but had found it a little hard to keep things lined up properly. So, he took White Out and made little vertical guidelines of white dots on his computer monitor to help him eyeball the alignment. Needles to say, I got him started with software that would do the alignment for him!
Our software has the capability to redo the indexes for individual sections of the program. I asked a client to do a certain section, because the letter writing part of the program is not seeing one of the databases. She asked her tech to do it, but the tech didn't want to do it without guidance.
I told him I can show him how to do it so he can run it himself, but he was insistent I come in a half hour earlier than my shift (unpaid) so I can do it for him.
Our software update takes about 30-45 minutes and there may be times when the screen just stays there while it's doing a table update, which causes Windows to say Not Responding.
Client decides to start the update 15 minutes before they're supposed to open. She panics when it's 5 minutes before she opens and she sees that the Window says not responding. I told her that there may be times when it's processing in the background. She wants to stop the update. I told her it's not possible because it would result in mismatched databases and program files. I told her I could restore to a previous version but it would also take about 15-20 minutes to find the backup and restore.
She sarcastically says "So you can't help me" and hangs up.
Tales From Technical Support Index
