D
Darryl
I have a problem that is very unusual. In essence, one of our staff can read
an excel spreadsheet, modify it, and save it, and close down, all apparently
successful. The only problem is that sometimes, not all the time, when she
goes to read the file she has just saved Excel complains that it is
unreadable. We are having trouble identifying any consistent behaviour linked
to those times where it becomes unreadable.
Some background.
I originally created the file using Excel 2003, and it has some reasonable
sophisticated macros that do things like querying an Oracle database. When I
transferred it to the network drive for production use, the end users were
unable to read it because they had Excel 2000. I saved it in Excel 95 format,
and then reloaded the macros by importing them. At that point, everything
works OK. All the macros do what they are supposed to do, and the spreadsheet
saves OK except for some spurious occasions. I have access to Excel 2000 via
a Citrix terminal. When the file becomes unreadable for the end-user, it is
not readable in the Citrix version either so I can confirm that. However I
cannot recreate the problem at all. For those who have to use this
spreadsheet, it happens about once per day or every two days, and they would
save it probably 5-10 times per day.
Another piece of the puzzle. This "corruption" has just happened again, and
I find that I can read the file perfectly well with Excel 2003. It is as if
it has reverted back to the 2003 file format, even though it has been saved
with Excel 2000.
Any suggestions?
Thanks in advance.
Darryl
an excel spreadsheet, modify it, and save it, and close down, all apparently
successful. The only problem is that sometimes, not all the time, when she
goes to read the file she has just saved Excel complains that it is
unreadable. We are having trouble identifying any consistent behaviour linked
to those times where it becomes unreadable.
Some background.
I originally created the file using Excel 2003, and it has some reasonable
sophisticated macros that do things like querying an Oracle database. When I
transferred it to the network drive for production use, the end users were
unable to read it because they had Excel 2000. I saved it in Excel 95 format,
and then reloaded the macros by importing them. At that point, everything
works OK. All the macros do what they are supposed to do, and the spreadsheet
saves OK except for some spurious occasions. I have access to Excel 2000 via
a Citrix terminal. When the file becomes unreadable for the end-user, it is
not readable in the Citrix version either so I can confirm that. However I
cannot recreate the problem at all. For those who have to use this
spreadsheet, it happens about once per day or every two days, and they would
save it probably 5-10 times per day.
Another piece of the puzzle. This "corruption" has just happened again, and
I find that I can read the file perfectly well with Excel 2003. It is as if
it has reverted back to the 2003 file format, even though it has been saved
with Excel 2000.
Any suggestions?
Thanks in advance.
Darryl