HELP

  • Thread starter Thread starter JohnUk
  • Start date Start date
J

JohnUk

Hi, I have built a workbook that has 22 tabs (11 of them
hidden)
Its fluctuates between 5mb and 7mb in size, even though
no extra information is added
It has in the region of 60 macros, to do different
functions, from getting from one page to another to
creating emails.
The workbook is used by 12 other people, and up until
recently it has been working fine.
It started with one of the 12. They had been working on
the workbook, closed it down - no problem, but when they
went to reopen it, it came up with a message "Unable to
read file", then once that had gone another message came
up saying -
"Errors were detected, but Microsoft Office Excel was
able to open the file by making the repairs listed below"
The list was the 28 pivot tables it had disabled, due to
integrity problems.
The problem has now spread to 3 others including myself.
I rebuilt all the pivot tables, but the problem still
happens.
We all use Windows XP Professional, I work on Office
2003, and the rest of the guys use Office 2002
Can anyone out there give me an explanation as to why
this has now started to happen, and hopefully give me a
solution before it spreads to everyone?
Many thanks in advance
John
PS We all also have Norton Antivirus software installed
 
Hi John,
The workbook is used by 12 other people, and up until
recently it has been working fine.
It started with one of the 12. They had been working on
the workbook, closed it down - no problem, but when they
went to reopen it, it came up with a message "Unable to
read file", then once that had gone another message came
up saying -
"Errors were detected, but Microsoft Office Excel was
able to open the file by making the repairs listed below"
Click to expand...

Sounds like a workbook corruption.

See

www.jkp-ads.com/CorruptFiles.htm

for some information.

Is this a shared workbook?

Regards,

Jan Karel Pieterse
Excel MVP
www.jkp-ads.com
 
Hi Jan,
Its one file that is then sent out to the other 12 guys,
so if one has a problem, they should all get the same
John
 
Hi John,
Its one file that is then sent out to the other 12 guys,
so if one has a problem, they should all get the same
John
Click to expand...

It may sometimes help to clean out the temp folder(s) of the offending
people's systems.
If the file contains controls on the sheets, Excel will create
temporary files with the emf extension in the temp folder. Sometimes
such a temp file gets corrupted, causing the file that they originate
from to cause havoc. After removing the emf files, things should work
OK again.

Regards,

Jan Karel Pieterse
Excel MVP
www.jkp-ads.com
 
Jan,
I have done a search on my drive for files with an .emf
extension, and it came up with one,"mso127D.emf" It
turned out to be a picture. Does this mean I have turned
a blank?
John
 
Hi John,
I have done a search on my drive for files with an .emf
extension, and it came up with one,"mso127D.emf" It
turned out to be a picture. Does this mean I have turned
a blank?
Click to expand...

No, they are all pictures (very likely of controls). Delete them.

Regards,

Jan Karel Pieterse
Excel MVP
www.jkp-ads.com
 
Hi: I had the same problem with a Pivot table I developed with Excel 2000 and
1 user saving his data with Excel 2003. Every time he saved it he got the
same message and the file became unabable to be read.

The solution: I had to develop the pivot tables with Excel 2003, and now can
save it with any version and works well so far. I guess there is a
compatibility problem among different excel versions when working with pivot
tables.
 
Guest said:
Hi: I had the same problem with a Pivot table I developed with Excel 2000 and
1 user saving his data with Excel 2003. Every time he saved it he got the
same message and the file became unabable to be read.

The solution: I had to develop the pivot tables with Excel 2003, and now can
save it with any version and works well so far. I guess there is a
compatibility problem among different excel versions when working with pivot
tables.
Click to expand...

I had many of the same problems. I changed the name of 'officeav.dll',
rebooted and the problem went away.

Try it
 
Back
Top