Re: Unable to Read File

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Steve (anonymous_at_discussions.microsoft.com)
Date: 07/06/04 

Date: Tue, 6 Jul 2004 09:55:47 -0700

Jim,

First, thanks for your reply.

MS Knowledgebase article (Q213879) doesn't offer any
help, other than to suggest I download some additional
code (which I did) and then contact Microsoft.

>From reading the article, it sounds like this is a known
problem and not specific to my computer or my usage
patterns.

I backup regularly, but don't believe this is a backup
issue. The file I created Sunday was unreadable Monday.
The file I created May 31, is now unreadable. However,
the files I created in April, March, February and January
are all readable. Strange. Further, when I recreated my
work yesterday (a sizable task) I saved the file without
using a password and can read it fine today; but the file
I created Sunday with a password is unreadable. My
conclusion: there's a bug in the password facility.

Steve
>-----Original Message-----
>If the suggestions in the MS Knowledgebase articles on
corrupted files have
>not helped you, you might have to look into data
recovery tools such as at
>http://www.conceptdata.com/excel/.
>
>You seem to have a pattern of getting corrupted files.
You'll absolutely
>need a system of backing up files in that case. In fact
everyone should
>backup important files. Also, if by any chance you are
saving files to
>floppy disks, you definitely want to stop that
practice. Floppy disks and
>Excel do not get along.
>
>--
>Jim Rech
>Excel MVP
>"Steve" <anonymous@discussions.microsoft.com> wrote in
message
>news:26b6d01c462d3$74ff0cb0$a401280a@phx.gbl...
>| I've recently begun receiving error message "Unable to
>| Read File" when trying to open a password protected
file.
>| I am able to open the Jan, Feb, Mar and Apr files
without
>| problem, but not the May file. Thinking it was a
fluke, I
>| spent a half-day yesterday creating a June file, but
>| returned, tried to open yesterday's file, and got the
>| same error message. I have now received the error
message
>| on two files (May and June), basically eliminating the
>| possibliity of a random fluke. From reading the
Microsoft
>| Knowledge Base, it appears that this may be a known
>| problem. Does anyone have any suggestions on how to get
>| around this problem? Thanks in advance.
>
>
>.
>

Quantcast