mcdst in action

bighornsheep

a similar situation occured at work, and I just thought I would post about it here as sort of a practice question.

You are the desktop support person of your department managing Windows XP professional desktops with Microsoft Office applications. A user calls you and states that there is data corruption in an excel file that she has been working on for many months.

The file is in a folder share located on your department server, and your system administrator is on holiday. You verify that no other files in the folder is corrupt, but the user insists that data is incorrect because dates and numbers appear as '######', what is the most likely cause of the problem?
A) The file is corrupt, restore a backup copy
Cells are locked
C) Cell Format needs to be configured
D) Cell is linked to an inaccessible location
E) Cell width needs to be configured

I overheard the situation and was able to provide the proper solution...heh....have fun~ and good luck!

D-boy

C) Cell Format needs to be configured

Just a guess!

SirDrago

Could be D, but i'm just guessing too.

spike_tomahawk

E: double click on the column line and it will auto size to the contents in the cell

sprkymrk

It's E. I've seen it happen before.

BTW - If it was indeed corrupted, and you had a smart admin, you could simply instruct the user to right click the file, go to properties and then previous versions. I love Shadow Copies.

bighornsheep

we have a winner! ...well.. two...
spike_tomahawk, sprkymrk

congrats! yup.....it's e), the width size needs to be increased.

well, now you know...

Orion82698

F. I hate Excel

I was going to say Back up or Shadow copy as well.

thumbs up to sprkymrk for that one

sprkymrk

G. Reboot
H. Reinstall Office

Orion82698

sprkymrk wrote:

G. Reboot
H. Reinstall Office

touche

sprkymrk

Believe it or not, I know a couple of "techs" that would have chosen reboot as the first thing, and if that didn't work they would reinstall. It's pretty much their standard operationg procedure; reboot, reinstall, rinse and repeat as necessary.

bighornsheep

sprkymrk wrote:

Believe it or not, I know a couple of "techs" that would have chosen reboot as the first thing, and if that didn't work they would reinstall. It's pretty much their standard operationg procedure; reboot, reinstall, rinse and repeat as necessary.

exactly why I posted this scenario with made up answers by me
an MCSA+MCDBA+CCNA said it's because of Office XP/Office 2003 issue.....

Orion82698

bighornsheep wrote:

sprkymrk wrote:

Believe it or not, I know a couple of "techs" that would have chosen reboot as the first thing, and if that didn't work they would reinstall. It's pretty much their standard operationg procedure; reboot, reinstall, rinse and repeat as necessary.

exactly why I posted this scenario with made up answers by me
an MCSA+MCDBA+CCNA said it's because of Office XP/Office 2003 issue.....

LOL... that's very typical where I work too. If you can't figure out the error or issue "It's got to a bug in the program"

BTW sprkymrk... I love your avitar! Is that Wilson Combat 1911?

sprkymrk

orion82698 wrote:

BTW sprkymrk... I love your avitar! Is that Wilson Combat 1911?

Thanks.
It's actually a Springfield. It's from their custom shop.

itdaddy

E:

bighornsheep

yes, i would agree and this would be my boss!