Lan based virus protection software can interfere with the save process and
cause this. See if you have eight character (no extension) machine named
files in the same directory. If so, see if you can open these in Excel.
Excel works with files using a temp file - (the machine named files above) -
and network permissions may be a consideration here. Here is some
supporting information (no specific solutions but may add to your
understanding of the problem)
XL: Delete Permissions Required to Save File on Network Server
XL: Temporary file Created When You Save a document
WD97: Info: Novel Network Privileges Required to Run Word
(Word and Excel save files the same way, I believe)
XL: Can't Create Copy of Module Sheet on Netware Server
Files Corrupted on Save: How to Troubleshoot Source of Problem
(this is more Win 95 based - but may be a nugget in here)
Saving from Word [Excel] for Windows Resets NTFS Security Permissions
(While this is specific to NT with NTFS, it has some general info)
XL: "Filename Is Not Valid" Error Saving or Opening File
When you open or save a file in Microsoft Excel, you may receive one of the
following error messages:
Filename is not valid
The file could not be accessed.
The path you entered, '<filename>', is too long. Enter a shorter path.
XL: Cannot Rename to '<File name>' Saving to Network Drive
XL2000: Files Corrupted on Save: How to TShoot Source of Problem
>I've got a recurring problem with Excel 2000 where my users are saving a
>worksheet and the next time (or sometime in the future) they try to open it
>they get the message "Unable to read file.". The files are being saved and
>accessed over a tcp/ip network.
>I've downloaded the .xla from Microsoft that reconstructs files - but it
>will not work on a file that is already damaged to the point of being
>unopenable. What I'm hoping for is a hint of what might be causing this to
>occur. Can anyone shed any light on this for me? TIA.