G
Guest
(Operating System Windows XP Home, Email Program Outlook Express 6, MS Word
2000 with ALL updates)
This week for the first time I have encountered a problem opening Word
documents attached to emails from friends. I save the attachment into my
"Received Files" folder, scan it for viruses and then open it. Word opens
and then I get the following message
"the document name or path os not valid. Try these suggestions
*check the file permissions for the document or drive
*use the "File Open" dialogue box to locate the document
(C:\...\some folder name which I can't find when I "search" for it\file name)
I have tried the suggestions. When I click on properties for the file I see
nothing unusual except under the heading "security" it reads "this file came
from another computer and might be blocked to help protect this computer".
Next to this is a button labelled "Unblock" Seems simple enough only even
after clicking on this button (which, by the way, makes the entire security
message and button disappear) I still get the same message when trying to
open the file.
I have unchecked the "Do not allow attachments to be saved or opened.."
option in Outlook Express, deleted the attachment from the computer, asked
for it to be resent and still get the same result.
I have deleted the attachment from the computer, re-installed Word (leaving
the "Do not allow..." option in OE unchecked) and asked the sender to resend
the attachment and STILL get the same result...
The odd thing is that this has happened with two Word attachments this week,
yet another Word attachment that I received opened just fine (like they used
to). The only difference I can see is that the file that DID open was
smaller (22kb). whereas the other two were 1.62Mb (included photos) and
617kb...
By the way I COULD open both of the files in Wordpad and read the text from
between the gobbledygook it shows for formatting and pictures...
WELL, I think I have fully explained the issue! I would appreciate it
if anyone can help me to resolve this problem sa that I can open these files
and not encounter this problem in future...
2000 with ALL updates)
This week for the first time I have encountered a problem opening Word
documents attached to emails from friends. I save the attachment into my
"Received Files" folder, scan it for viruses and then open it. Word opens
and then I get the following message
"the document name or path os not valid. Try these suggestions
*check the file permissions for the document or drive
*use the "File Open" dialogue box to locate the document
(C:\...\some folder name which I can't find when I "search" for it\file name)
I have tried the suggestions. When I click on properties for the file I see
nothing unusual except under the heading "security" it reads "this file came
from another computer and might be blocked to help protect this computer".
Next to this is a button labelled "Unblock" Seems simple enough only even
after clicking on this button (which, by the way, makes the entire security
message and button disappear) I still get the same message when trying to
open the file.
I have unchecked the "Do not allow attachments to be saved or opened.."
option in Outlook Express, deleted the attachment from the computer, asked
for it to be resent and still get the same result.
I have deleted the attachment from the computer, re-installed Word (leaving
the "Do not allow..." option in OE unchecked) and asked the sender to resend
the attachment and STILL get the same result...
The odd thing is that this has happened with two Word attachments this week,
yet another Word attachment that I received opened just fine (like they used
to). The only difference I can see is that the file that DID open was
smaller (22kb). whereas the other two were 1.62Mb (included photos) and
617kb...
By the way I COULD open both of the files in Wordpad and read the text from
between the gobbledygook it shows for formatting and pictures...
WELL, I think I have fully explained the issue! I would appreciate it
if anyone can help me to resolve this problem sa that I can open these files
and not encounter this problem in future...