Save button flickers in the "save as" window

[pierre.daubresse]

We have several workstations in my department, all equipped with MS
Office 2004, running on Mac OS X Tiger. One person experimented twice
the following problem, with Excel sheets she received by e-mail.
She can open the document and work with it, but when she does a "save
as", the "save as" window opens and the application doesn't respond
anymore, with the save button flickering all the time. No other action
is possible than quitting Excel.
I updated MS office and OS X to the latest version, but it didn't
solve the problem. I also trashed the preferences files but it didn't
help. If a open the document on another computer, it works and I can
save it without any problem.
Thanks for your help,

Pierre Daubresse

 

[JE McGimpsey]

We have several workstations in my department, all equipped with MS
Office 2004, running on Mac OS X Tiger. One person experimented twice
the following problem, with Excel sheets she received by e-mail.
She can open the document and work with it, but when she does a "save
as", the "save as" window opens and the application doesn't respond
anymore, with the save button flickering all the time. No other action
is possible than quitting Excel.
I updated MS office and OS X to the latest version, but it didn't
solve the problem. I also trashed the preferences files but it didn't
help. If a open the document on another computer, it works and I can
save it without any problem.

Does this happen in any other application? MacOffice uses Mac OSX system
dialogs for saving, so if it's only happening on one machine (and after
trashing preferences), I'd suspect a system-related cause, though I
can't think of anything specific that would cause this.

I suppose one should check for macros in the emailed workbook, but any
Before_Save event macro should have completed prior to displaying the
Save As dialog.

Is it only the one file? Where is your user trying to save the file? If
it's a network directory, are permissions set correctly for her machine?

And while I don't see that it will necessarily help, resetting disk
permissions (using the Disk Utility application) has fixed other weird
I/O problems.