F
fellow.anna
Hi
I am on an iBook G4, Tiger 10.4.10, Microsoft Office Student Edition
2004, all current updates in order.
After I ran the most recent system update, i have a problem with
opening Excel files. If I open Excel application, or if I doubleclick
on any excel file to open, I get this error message:
<a href="http://photobucket.com" target="_blank"><img src="http://
img.photobucket.com/albums/v208/obraztsova/excelmessage.jpg"
border="0" alt="Photo Sharing and Video Hosting at Photobucket"></a>
If I click CANCEL and then go via File --> Open menu to locate the
desired file, everything opens just fine.
I have had this problem before (maybe 2 years ago), and at the time I
was advised to delete a .plist file associated with Excel, restart
computer, and reopen Excel (it recreates the .plist file), and it
seemed to have worked. This time, however, this trick does not solve
the problem.
I've repaired permissions, ran Yasu (clean up app), and still -- the
same error appears.
Has anyone seen anything similar? What might be your suggestion to
resolve this?
Thank you for your advice!
I am on an iBook G4, Tiger 10.4.10, Microsoft Office Student Edition
2004, all current updates in order.
After I ran the most recent system update, i have a problem with
opening Excel files. If I open Excel application, or if I doubleclick
on any excel file to open, I get this error message:
<a href="http://photobucket.com" target="_blank"><img src="http://
img.photobucket.com/albums/v208/obraztsova/excelmessage.jpg"
border="0" alt="Photo Sharing and Video Hosting at Photobucket"></a>
If I click CANCEL and then go via File --> Open menu to locate the
desired file, everything opens just fine.
I have had this problem before (maybe 2 years ago), and at the time I
was advised to delete a .plist file associated with Excel, restart
computer, and reopen Excel (it recreates the .plist file), and it
seemed to have worked. This time, however, this trick does not solve
the problem.
I've repaired permissions, ran Yasu (clean up app), and still -- the
same error appears.
Has anyone seen anything similar? What might be your suggestion to
resolve this?
Thank you for your advice!